← previous blocknext block →recent activity
Analyzing
Block #110,392,436
21 transactions · 21 stateful · 2026-10-04 06:16:02 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #110,392,436 · 21 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
1w03w04w111w012w113w114w215w017w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39d0cb3b…de5c
0x34b655…2a6f
6 touches
3 conflicts
0x81622051…deeb
0x34b655…2a6f
6 touches
3 conflicts
0x0fcb5a25…9f42
0x34b655…2a6f
4 touches
1 conflict
0x2926f9a8…e952
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xce7a3604…c4b6
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 0x39d0cb3b28…d2de5c
Audit this contract →
← previous block·next block →recent activity