← previous blocknext block →recent activity
Analyzing
Block #110,208,025
17 transactions · 14 stateful · 2026-10-03 14:48:07 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #110,208,025 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x060ca9f4…9272
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0152498a…018b
0x34b655…2a6f
2 touches
0 conflicts
0x132b9de1…183b
0x34b655…2a6f
2 touches
0 conflicts
0x1c0ff00b…ffac
0x34b655…2a6f
2 touches
0 conflicts
0x6e360a5d…8836
0x34b655…2a6f
2 touches
0 conflicts
0x75f36d60…8556
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x060ca9f49e…6a9272
Audit this contract →
← previous block·next block →recent activity