← previous blocknext block →recent activity
Analyzing
Block #110,375,851
12 transactions · 11 stateful · 2026-10-04 04:52:35 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #110,375,851 · 12 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
2w03w14w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15d039e7…4bb6
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
2 touches
0 conflicts
0x8a2657f5…e008
0x34b655…2a6f
2 touches
0 conflicts
0x93269085…a48f
0x34b655…2a6f
2 touches
0 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
2 touches
0 conflicts
0x9f63b181…919d
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 0x15d039e716…294bb6
Audit this contract →
← previous block·next block →recent activity