← previous blocknext block →recent activity
Analyzing
Block #86,764,620
16 transactions · 15 stateful · 2026-07-10 04:14:30 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
0.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,764,620 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w39w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1c03f81f…b304
0x34b655…2a6f
4 touches
1 conflict
0x2aad10f1…ded8
0x34b655…2a6f
4 touches
1 conflict
0x3893ea3a…31c3
0x34b655…2a6f
4 touches
1 conflict
0x40f341a8…1bba
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 0x5655f5c3b4…dd6b75
Audit this contract →
← previous block·next block →recent activity