← previous blocknext block →recent activity
Analyzing
Block #83,577,303
13 transactions · 13 stateful · 2026-06-25 09:54:28 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,577,303 · 13 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
1w03w14w25w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x4cd6928f…1a19
0x2a68ba…90c5
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x06a3873f…b120
0xa6afd3…d132
3 touches
1 conflict
0x9d6caa0a…6ad7
0xa6afd3…d132
3 touches
1 conflict
0xca29d1b7…4b62
0x34b655…2a6f
2 touches
0 conflicts
0xe64e6363…e676
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-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity