← previous blocknext block →recent activity
Analyzing
Block #108,602,802
33 transactions · 29 stateful · 2026-09-28 00:00:58 UTC
Parallelism
82/100
Blocked
52%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,602,802 · 33 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w28w110w111w012w014w115w217w322w125w326w427w530w131w432w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x24e97cfb…8012
0xd32edf…ff58
11 touches
15 conflicts
0x348fda08…7e96
0x065c9d…c394
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xa4fd1b6f…d737
0x1b6862…e19c
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity