← previous blocknext block →recent activity
Analyzing
Block #86,634,564
13 transactions · 10 stateful · 2026-07-09 13:44:38 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,634,564 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x460a21c2…87f1
0x34b655…2a6f
4 touches
1 conflict
0x10425555…9dcf
0x34b655…2a6f
2 touches
0 conflicts
0x18de899b…7b35
0x34b655…2a6f
2 touches
0 conflicts
0x3133f94b…f76b
0x34b655…2a6f
2 touches
0 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
2 touches
0 conflicts
0x5da07818…5ea1
0x34b655…2a6f
2 touches
0 conflicts
0x63c900f4…2600
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity