← previous blocknext block →recent activity
Analyzing
Block #103,222,317
29 transactions · 25 stateful · 2026-09-09 03:50:33 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,222,317 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w09w111w316w017w121w122w323w426w027w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xc21def1b…c24d
0xa6afd3…d132
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x34ae4d…3fc5
6 touches
3 conflicts
0x0b104f98…d9ee
0xc8689a…ee79
6 touches
3 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity