← previous blocknext block →recent activity
Analyzing
Block #83,970,306
13 transactions · 11 stateful · 2026-06-27 05:36:20 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,970,306 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cdff908…f6e6
0xa6afd3…d132
4 touches
1 conflict
0x028181c2…3705
0x065c9d…c394
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x21252bd8…a647
0x0594c7…a3be
2 touches
0 conflicts
0x69f074ac…cf1a
0x0594c7…a3be
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 0x3cdff90814…ccf6e6
Audit this contract →
← previous block·next block →recent activity