← previous blocknext block →recent activity
Analyzing
Block #86,153,503
31 transactions · 24 stateful · 2026-07-07 08:09:15 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,153,503 · 31 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
1w06w07w010w011w112w213w317w122w423w426w128w029w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x10d9dbcb…9fdb
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x92132ed7…2722
0x34b655…2a6f
8 touches
6 conflicts
0xde398ff4…00ca
0x34b655…2a6f
8 touches
6 conflicts
0xec0e0220…cb90
0x34b655…2a6f
8 touches
6 conflicts
0xc3688185…9b36
0x34b655…2a6f
6 touches
3 conflicts
0xdc6384c6…599c
0xd32edf…ff58
5 touches
3 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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity