← previous blocknext block →recent activity
Analyzing
Block #87,911,411
9 transactions · 9 stateful · 2026-07-15 12:03:26 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,911,411 · 9 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x5a36d0c8…12e2
0x34b655…2a6f
6 touches
3 conflicts
0x5a36d0c8…12e3
0x34b655…2a6f
6 touches
3 conflicts
0x72880226…1435
0x34b655…2a6f
6 touches
3 conflicts
0xb3ae4660…5f75
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x64430813…6bd4
0x34b655…2a6f
4 touches
1 conflict
0x8392c505…cc71
0x34b655…2a6f
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity