← previous blocknext block →recent activity
Analyzing
Block #87,724,250
18 transactions · 16 stateful · 2026-07-14 15:11:30 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,724,250 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w18w09w210w111w115w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9eb155db…f714
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x191c9934…f4f4
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3f33f55b…32cb
0x34b655…2a6f
4 touches
1 conflict
0x478f4afc…adff
0x34b655…2a6f
4 touches
1 conflict
0x59267ce8…cbbf
0x34b655…2a6f
4 touches
1 conflict
0x7b3f8378…b37d
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 0x9eb155db95…01f714
Audit this contract →
← previous block·next block →recent activity