← previous blocknext block →recent activity
Analyzing
Block #107,806,029
25 transactions · 19 stateful · 2026-09-25 05:10:34 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,806,029 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w113w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x19e49883…3293
0x851145…3f07
4 touches
1 conflict
0xcfeed415…e4ab
0x851145…3f07
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c5
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c7
0x508254…98bd
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity