← previous blocknext block →recent activity
Analyzing
Block #86,617,191
13 transactions · 12 stateful · 2026-07-09 11:48:33 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,617,191 · 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
2w07w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xceccdd75…ace1
0x065c9d…c394
3 touches
1 conflict
0x12bbe71a…4eb3
0x34b655…2a6f
2 touches
0 conflicts
0x19a8c371…b8ce
0x34b655…2a6f
2 touches
0 conflicts
0x21d72491…a535
0x34b655…2a6f
2 touches
0 conflicts
0x2b7950c1…2342
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity