← previous blocknext block →recent activity
Analyzing
Block #87,052,823
13 transactions · 13 stateful · 2026-07-11 12:20:33 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,052,823 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9199a85a…acd9
0x34b655…2a6f
4 touches
1 conflict
0x3219a96c…4e19
0x34b655…2a6f
4 touches
1 conflict
0x0e53397f…faa1
0x34b655…2a6f
2 touches
0 conflicts
0x0e65cb4f…6c25
0x34b655…2a6f
2 touches
0 conflicts
0x3d0454c5…6ab5
0x34b655…2a6f
2 touches
0 conflicts
0x777c0352…4d8c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity