← previous blocknext block →recent activity
Analyzing
Block #110,210,348
16 transactions · 16 stateful · 2026-10-03 14:59:49 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #110,210,348 · 16 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
3w04w15w06w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xb686e6f5…f6d1
0xc8689a…ee79
4 touches
1 conflict
0x46279ae7…20dd
0x34ae4d…3fc5
2 touches
0 conflicts
0x7b6b88fb…1109
0x34ae4d…3fc5
2 touches
0 conflicts
0x2ee94fa9…60a4
0x508254…98bd
2 touches
0 conflicts
0x2ee94fa9…60b2
0x508254…98bd
2 touches
0 conflicts
0x2ee94fa9…60fa
0x508254…98bd
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity