← previous blocknext block →recent activity
Analyzing
Block #110,220,858
16 transactions · 15 stateful · 2026-10-03 15:52:46 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,220,858 · 16 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
1w03w04w17w08w19w211w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x3b38ded9…9943
0x34b655…2a6f
5 touches
3 conflicts
0xe01c766d…74bd
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3237eed8…9934
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xfdd40e24dd…99dca0
Audit this contract →
← previous block·next block →recent activity