← previous blocknext block →recent activity
Analyzing
Block #85,984,313
13 transactions · 12 stateful · 2026-07-06 13:19:43 UTC
Parallelism
54/100
Blocked
58%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,984,313 · 13 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
1w02w03w04w15w18w29w310w411w512w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea9e7e38…819b
0x34b655…2a6f
8 touches
6 conflicts
0x0f21840f…6cde
0x34b655…2a6f
6 touches
3 conflicts
0x4a396071…68ee
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x7fffd49d…772a
0x34b655…2a6f
4 touches
1 conflict
0xaf9bf782…e3d9
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity