← previous blocknext block →recent activity
Analyzing
Block #87,410,358
16 transactions · 14 stateful · 2026-07-13 04:11:28 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,410,358 · 16 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
1w02w03w14w25w36w48w011w512w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05a7428b…ddf3
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x286711a5…b3bf
0x34b655…2a6f
8 touches
6 conflicts
0x2b111712…0e59
0x34b655…2a6f
8 touches
6 conflicts
0x427f51fd…bd80
0x34b655…2a6f
8 touches
6 conflicts
0x61a218f6…8b88
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x801058a8…5bc3
0x34b655…2a6f
8 touches
6 conflicts
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
10 conflicts on slot 0x05a7428b79…6cddf3
Audit this contract →
← previous block·next block →recent activity