← previous blocknext block →recent activity
Analyzing
Block #108,275,970
38 transactions · 30 stateful · 2026-09-26 20:35:46 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
1.37
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,275,970 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w07w19w010w113w215w217w019w121w323w224w325w426w529w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
12 touches
15 conflicts
0x0778475b…bd75
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x00000000…0002
0x125f12…a50b
10 touches
10 conflicts
0xbcb0ff94…de67
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x013bb37b…eb49
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity