← previous blocknext block →recent activity
Analyzing
Block #110,386,308
18 transactions · 17 stateful · 2026-10-04 05:45:12 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,386,308 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w013w115w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4656137…5858
0x34b655…2a6f
6 touches
3 conflicts
0x8c211514…b757
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdfa2f3cb…b8a6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0053
0x1b6862…e19c
4 touches
1 conflict
0x2dbb4a74…8312
0x1b6862…e19c
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 0xb465613784…635858
Audit this contract →
← previous block·next block →recent activity