← previous blocknext block →recent activity
Analyzing
Block #85,918,618
15 transactions · 8 stateful · 2026-07-06 06:01:22 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,918,618 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5300ada7…f01e
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
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 0x5300ada79b…f6f01e
Audit this contract →
← previous block·next block →recent activity