← previous blocknext block →recent activity
Analyzing
Block #108,279,195
35 transactions · 30 stateful · 2026-09-26 20:52:01 UTC
Parallelism
80/100
Blocked
60%
Avg conflicts / tx
1.34
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,279,195 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w27w38w09w114w121w226w528w429w530w232w6
- 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
10 touches
10 conflicts
0xdfa159d0…1576
0x065c9d…c394
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
8 touches
6 conflicts
0xbaf77397…e798
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xcb40ae17…7323
0xd32edf…ff58
7 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