← previous blocknext block →recent activity
Analyzing
Block #110,308,269
27 transactions · 23 stateful · 2026-10-03 23:12:34 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,308,269 · 27 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
6w07w18w015w017w120w121w222w223w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
6 touches
3 conflicts
0x7954ece9…fef0
0x34b655…2a6f
6 touches
3 conflicts
0x08eb7666…9364
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x42eb24cc…8882
0x34b655…2a6f
4 touches
1 conflict
0x4ab23153…8f44
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
3 conflicts on slot 0xe720a4c698…508eb0
Audit this contract →
← previous block·next block →recent activity