← previous blocknext block →recent activity
Analyzing
Block #86,674,304
13 transactions · 11 stateful · 2026-07-09 18:11:18 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,674,304 · 13 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
6w08w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcc2ea3e…8ea3
0x34b655…2a6f
4 touches
1 conflict
0x459573ed…fbbe
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x450d6fa6…350d
0x34b655…2a6f
2 touches
0 conflicts
0x656bd53e…af4e
0x34b655…2a6f
2 touches
0 conflicts
0x71a04919…41db
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
1 conflict on slot 0xbcc2ea3eea…278ea3
Audit this contract →
← previous block·next block →recent activity