← previous blocknext block →recent activity
Analyzing
Block #87,349,469
9 transactions · 6 stateful · 2026-07-12 21:24:10 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,349,469 · 9 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xcf5ef070…7d4f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0001c357…b61b
0x34b655…2a6f
2 touches
0 conflicts
0x00e76a35…df2b
0x34b655…2a6f
2 touches
0 conflicts
0x0b277fb8…2d81
0x34b655…2a6f
2 touches
0 conflicts
0x0b277fb8…2d82
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