← previous blocknext block →recent activity
Analyzing
Block #110,207,819
21 transactions · 17 stateful · 2026-10-03 14:47:05 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #110,207,819 · 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
7w010w011w112w216w017w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x5bf29e70…4100
0x34b655…2a6f
6 touches
3 conflicts
0x8c211514…b757
0x34b655…2a6f
6 touches
3 conflicts
0xb4656137…5858
0x34b655…2a6f
6 touches
3 conflicts
0x1c385c8c…a0fb
0x34b655…2a6f
5 touches
3 conflicts
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f394…c5fd
0x34b655…2a6f
4 touches
1 conflict
0x6419eb11…3680
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity