← previous blocknext block →recent activity
Analyzing
Block #100,122,447
16 transactions · 14 stateful · 2026-08-29 07:16:49 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,122,447 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w112w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0xdb88ce18…68ca
0x8964d7…10f8
6 touches
3 conflicts
0xdb88ce18…68cb
0x8964d7…10f8
6 touches
3 conflicts
0xdb88ce18…68ce
0x8964d7…10f8
6 touches
3 conflicts
0xdb88ce18…68cf
0x8964d7…10f8
6 touches
3 conflicts
0xdb88ce18…68d1
0x8964d7…10f8
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-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity