← previous blocknext block →recent activity
Analyzing
Block #108,503,315
21 transactions · 21 stateful · 2026-09-27 15:40:00 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,503,315 · 21 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
1w02w03w14w25w19w010w111w212w313w414w515w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x588380ee…0a5c
0x34b655…2a6f
8 touches
6 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x6aeef401…c7f2
0x34b655…2a6f
6 touches
3 conflicts
0xe3fa5262…0e0c
0x34b655…2a6f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity