← previous blocknext block →recent activity
Analyzing
Block #86,713,176
17 transactions · 11 stateful · 2026-07-09 22:30:40 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,713,176 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbf50b38…ac8c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb52189ea…8281
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9e70dadd…810e
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 0xdbf50b38a6…22ac8c
Audit this contract →
← previous block·next block →recent activity