← previous blocknext block →recent activity
Analyzing
Block #87,056,612
14 transactions · 13 stateful · 2026-07-11 12:45:56 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,056,612 · 14 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
6w07w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83bf1cc7…260e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdeba9876…6ad5
0x34b655…2a6f
4 touches
1 conflict
0xe88872e2…9975
0x34b655…2a6f
4 touches
1 conflict
0x1d8ad270…4c7d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x9accd401…78db
0x34b655…2a6f
4 touches
1 conflict
0xb671c17c…25a4
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 0x83bf1cc7fb…18260e
Audit this contract →
← previous block·next block →recent activity