← previous blocknext block →recent activity
Analyzing
Block #105,843,644
20 transactions · 17 stateful · 2026-09-18 08:29:03 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,843,644 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w113w014w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x27a04273…27c5
0x065c9d…c394
8 touches
6 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x2212375d…2720
0x065c9d…c394
5 touches
3 conflicts
0x9ba8ae4a…d706
0x065c9d…c394
5 touches
3 conflicts
0xcfa51d03…2ac9
0x065c9d…c394
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
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