← previous blocknext block →recent activity
Analyzing
Block #108,923,158
47 transactions · 31 stateful · 2026-09-29 02:57:00 UTC
Parallelism
89/100
Blocked
58%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,923,158 · 47 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
6w07w010w111w212w113w215w016w117w218w320w422w023w135w441w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
8 touches
6 conflicts
0x32bf5581…7b3c
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity