← previous blocknext block →recent activity
Analyzing
Block #112,610,397
21 transactions · 21 stateful · 2026-10-12 00:21:42 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,610,397 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w09w011w112w213w314w415w516w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x3e04662b…0da8
0x1b6862…e19c
8 touches
6 conflicts
0x6e91ba2c…e8e2
0xd32edf…ff58
7 touches
6 conflicts
0x319f3906…9640
0x1b6862…e19c
4 touches
1 conflict
0x4b2a9f64…3a39
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
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
10 conflicts on slot 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity