← previous blocknext block →recent activity
Analyzing
Block #108,549,911
28 transactions · 24 stateful · 2026-09-27 19:34:33 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,549,911 · 28 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
2w04w17w09w110w213w016w118w119w221w322w424w025w126w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0002
0x125f12…a50b
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0xef376c26…d837
0xd32edf…ff58
5 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