← previous blocknext block →recent activity
Analyzing
Block #108,276,373
27 transactions · 20 stateful · 2026-09-26 20:37:48 UTC
Parallelism
78/100
Blocked
30%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,276,373 · 27 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
2w06w17w212w319w422w525w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x726dcc07…6669
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x8e485ef0…8a8a
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xacfa70ef…1f78
0xba1333…9ba9
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0xc061cc51…c18a
0x754704…b603
2 touches
0 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: MarginAccount
15 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity