← previous blocknext block →recent activity
Analyzing
Block #83,843,751
20 transactions · 18 stateful · 2026-06-26 15:32:38 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,843,751 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w19w210w113w014w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb983f9fc…9b91
0xdde003…c9a4
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0016
0x8fbe07…71b6
4 touches
1 conflict
0x9f6a1e31…7de3
0x8fbe07…71b6
4 touches
1 conflict
0xcac3298e…53c9
0x8fbe07…71b6
4 touches
1 conflict
0x2d5c395b…6b5a
0xa6afd3…d132
4 touches
1 conflict
0x7c5260f4…bd96
0xa6afd3…d132
4 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity