← previous blocknext block →recent activity
Analyzing
Block #111,849,506
19 transactions · 19 stateful · 2026-10-09 08:33:24 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #111,849,506 · 19 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
1w02w13w24w35w08w09w110w011w112w213w314w415w517w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd73d5ed…fe05
0x34b655…2a6f
12 touches
15 conflicts
0xba5743c7…21c6
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x933d449c…8f2e
0xd32edf…ff58
9 touches
10 conflicts
0x063eca74…c2e2
0x1b6862…e19c
8 touches
6 conflicts
0x5c421c70…c2f2
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
15 conflicts on slot 0xdd73d5ed86…5dfe05
Audit this contract →
← previous block·next block →recent activity