← previous blocknext block →recent activity
Analyzing
Block #86,712,451
14 transactions · 12 stateful · 2026-07-09 22:25:49 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,712,451 · 14 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
3w04w16w08w19w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x122c41a2…05f5
0x34b655…2a6f
4 touches
1 conflict
0x1bfc029c…f91e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x311f801b…dc74
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x3bc7cb73…e46d
0x34b655…2a6f
4 touches
1 conflict
0x511ecf07…8ed0
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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
1 conflict on slot 0x122c41a218…6405f5
Audit this contract →
← previous block·next block →recent activity