← previous blocknext block →recent activity
Analyzing
Block #87,341,326
10 transactions · 10 stateful · 2026-07-12 20:29:46 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,341,326 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1852cfff…85ee
0x34b655…2a6f
2 touches
0 conflicts
0x19123d86…b667
0x34b655…2a6f
2 touches
0 conflicts
0x2bfdcf09…4cd4
0x34b655…2a6f
2 touches
0 conflicts
0x3e8e5402…4739
0x34b655…2a6f
2 touches
0 conflicts
0x407a239a…6d1b
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity