← previous blocknext block →recent activity
Analyzing
Block #86,799,881
15 transactions · 13 stateful · 2026-07-10 08:09:51 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,799,881 · 15 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
1w02w14w05w18w19w210w311w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee06e767…00d6
0x34b655…2a6f
6 touches
3 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x26064b2b…62b5
0x34b655…2a6f
4 touches
1 conflict
0x346e6e22…8deb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e66a473…9fe8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
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 0xee06e76704…0e00d6
Audit this contract →
← previous block·next block →recent activity