← previous blocknext block →recent activity
Analyzing
Block #86,315,713
13 transactions · 11 stateful · 2026-07-08 02:12:20 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,315,713 · 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
2w05w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf912a2c1…76c2
0x34b655…2a6f
4 touches
1 conflict
0x2c75ca93…a569
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0xa8b18ba0…f380
0x34b655…2a6f
4 touches
1 conflict
0xb835d684…089c
0x34b655…2a6f
4 touches
1 conflict
0xc62b9957…0d72
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 0xf912a2c101…4576c2
Audit this contract →
← previous block·next block →recent activity