← previous blocknext block →recent activity
Analyzing
Block #87,453,487
9 transactions · 8 stateful · 2026-07-13 08:59:49 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,453,487 · 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
1w03w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdc80bf7…e947
0x34b655…2a6f
6 touches
3 conflicts
0xd2d3fe13…b828
0x34b655…2a6f
4 touches
1 conflict
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0xc71887ae…9f3b
0x34b655…2a6f
4 touches
1 conflict
0xcc06b563…c7fc
0x34b655…2a6f
4 touches
1 conflict
0xd2d3fe13…b827
0x34b655…2a6f
4 touches
1 conflict
0x43a0d4c9…ee25
0x34b655…2a6f
4 touches
1 conflict
0x65851f64…529b
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 0xbdc80bf733…aae947
Audit this contract →
← previous block·next block →recent activity