← previous blocknext block →recent activity
Analyzing
Block #86,692,283
13 transactions · 11 stateful · 2026-07-09 20:11:15 UTC
Parallelism
69/100
Blocked
45%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,692,283 · 13 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
2w03w16w07w18w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01a08f7d…dec6
0x34b655…2a6f
4 touches
1 conflict
0x1bfc029c…f91e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x3cd5188c…f3d2
0x34b655…2a6f
4 touches
1 conflict
0x5d8c7f22…4881
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x65033350…9b21
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 0x01a08f7dea…2ddec6
Audit this contract →
← previous block·next block →recent activity