← previous blocknext block →recent activity
Analyzing
Block #86,924,274
11 transactions · 7 stateful · 2026-07-10 22:01:40 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,924,274 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9138a113…0d5f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xbde30d77…b032
0x34b655…2a6f
4 touches
1 conflict
0x206d06f5…48d3
0x34b655…2a6f
2 touches
0 conflicts
0x2ac830b6…080a
0x34b655…2a6f
2 touches
0 conflicts
0x2d7ea048…d78e
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 0x9138a113b1…c30d5f
Audit this contract →
← previous block·next block →recent activity