← previous blocknext block →recent activity
Analyzing
Block #110,220,642
21 transactions · 19 stateful · 2026-10-03 15:51:40 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #110,220,642 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w110w012w114w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0058
0x1b6862…e19c
8 touches
6 conflicts
0x5c421c70…c2f2
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity