← previous blocknext block →recent activity
Analyzing
Block #106,790,691
41 transactions · 32 stateful · 2026-09-21 15:57:31 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,790,691 · 41 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
4w05w16w27w011w113w318w019w321w023w224w325w126w429w431w432w533w638w139w240w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 conflicts
0x80d7dd57…9408
0xd32edf…ff58
7 touches
6 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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