← previous blocknext block →recent activity
Analyzing
Block #86,809,493
11 transactions · 9 stateful · 2026-07-10 09:14:05 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,809,493 · 11 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x44d24653…fa2f
0x34b655…2a6f
4 touches
1 conflict
0x698e3c53…a4c4
0x34b655…2a6f
4 touches
1 conflict
0x259f3ba0…a139
0x34b655…2a6f
2 touches
0 conflicts
0x32646adf…e05d
0x34b655…2a6f
2 touches
0 conflicts
0x44231245…5442
0x34b655…2a6f
2 touches
0 conflicts
0x44485f70…b1ac
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity