← previous blocknext block →recent activity
Analyzing
Block #87,264,951
12 transactions · 10 stateful · 2026-07-12 11:59:02 UTC
Parallelism
58/100
Blocked
40%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,264,951 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xf7210dcc…4065
0x34b655…2a6f
4 touches
1 conflict
0xe6da3556…9a23
0x34b655…2a6f
4 touches
1 conflict
0xea297ef6…552d
0x34b655…2a6f
4 touches
1 conflict
0xea297ef6…552e
0x34b655…2a6f
4 touches
1 conflict
0x3c62e153…ea69
0x34b655…2a6f
4 touches
1 conflict
0x3def7c2a…59e0
0x34b655…2a6f
4 touches
1 conflict
0x5571e830…9cea
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity