← previous blocknext block →recent activity
Analyzing
Block #87,517,803
19 transactions · 15 stateful · 2026-07-13 16:10:06 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,517,803 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w29w010w111w012w113w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x9c1e34a2…a218
0x34b655…2a6f
6 touches
3 conflicts
0x913ebf0e…d816
0x34b655…2a6f
4 touches
1 conflict
0x9f874527…4f85
0x34b655…2a6f
4 touches
1 conflict
0xa922f0a0…54c3
0x34b655…2a6f
4 touches
1 conflict
0x09a15b10…2639
0x754704…b603
4 touches
1 conflict
0x5149ba0e…d954
0x754704…b603
4 touches
1 conflict
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
3 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity