← previous blocknext block →recent activity
Analyzing
Block #108,796,670
40 transactions · 29 stateful · 2026-09-28 16:17:30 UTC
Parallelism
82/100
Blocked
59%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,796,670 · 40 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
1w02w03w04w16w27w39w413w114w115w116w433w535w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xffe431af…8faa
0x065c9d…c394
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
10 touches
10 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
10 touches
10 conflicts
0x06e40499…165e
0x34ae4d…3fc5
10 touches
10 conflicts
0x1b60b708…5b4b
0x34ae4d…3fc5
10 touches
10 conflicts
0x6235638c…6438
0x1b6862…e19c
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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity