← previous blocknext block →recent activity
Analyzing
Block #86,504,420
12 transactions · 10 stateful · 2026-07-08 23:13:14 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,504,420 · 12 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
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7e10454f…4d9e
0xa6afd3…d132
4 touches
1 conflict
0xb43dc900…22f2
0xa6afd3…d132
4 touches
1 conflict
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0x703b861a…cbe3
0x188d58…ea8e
2 touches
0 conflicts
0x703b861a…cbe5
0x188d58…ea8e
2 touches
0 conflicts
0x7ac76f4e…ad6a
0x188d58…ea8e
2 touches
0 conflicts
0x7ac76f4e…ad6c
0x188d58…ea8e
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-WETH/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity