← previous blocknext block →recent activity
Analyzing
Block #86,988,678
12 transactions · 11 stateful · 2026-07-11 05:11:58 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,988,678 · 12 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
2w03w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf47a88f…7b7e
0x34b655…2a6f
6 touches
3 conflicts
0xbf47a88f…7b7f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc50ac7d4…e964
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x1ed62880…5619
0x34b655…2a6f
5 touches
3 conflicts
0x85dcdf9d…1873
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
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
3 conflicts on slot 0xbf47a88f30…7d7b7e
Audit this contract →
← previous block·next block →recent activity