← previous blocknext block →recent activity
Analyzing
Block #87,913,220
24 transactions · 21 stateful · 2026-07-15 12:15:32 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,913,220 · 24 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
5w06w07w18w29w210w316w117w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30f3ece3…c237
0x34b655…2a6f
6 touches
3 conflicts
0x2000b734…5e5a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x109e6370…4cb8
0x34b655…2a6f
4 touches
1 conflict
0x109e6370…4cb9
0x34b655…2a6f
4 touches
1 conflict
0x2fead171…13d6
0x34b655…2a6f
4 touches
1 conflict
0x3a4908f6…7482
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 0x30f3ece315…53c237
Audit this contract →
← previous block·next block →recent activity