← previous blocknext block →recent activity
Analyzing
Block #87,410,969
16 transactions · 13 stateful · 2026-07-13 04:15:35 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,410,969 · 16 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
2w03w14w05w17w08w09w111w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05a7428b…ddf3
0x34b655…2a6f
6 touches
3 conflicts
0x086db8fc…0024
0x34b655…2a6f
6 touches
3 conflicts
0x108b29a6…8c76
0x34b655…2a6f
4 touches
1 conflict
0x1a28e34b…1404
0x34b655…2a6f
4 touches
1 conflict
0x1d73754c…2e95
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x3083951a…4fa0
0x34b655…2a6f
4 touches
1 conflict
0x39931443…c31d
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 0x05a7428b79…6cddf3
Audit this contract →
← previous block·next block →recent activity