← previous blocknext block →recent activity
Analyzing
Block #86,830,468
13 transactions · 9 stateful · 2026-07-10 11:34:30 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,830,468 · 13 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe8377f79…5f5e
0x34b655…2a6f
4 touches
1 conflict
0x01521950…6f17
0x34b655…2a6f
2 touches
0 conflicts
0x0682a731…d1e7
0x34b655…2a6f
2 touches
0 conflicts
0x071109d1…e04a
0x34b655…2a6f
2 touches
0 conflicts
0x0b277fb8…2d81
0x34b655…2a6f
2 touches
0 conflicts
0x0e60b9a9…253a
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity