← previous blocknext block →recent activity
Analyzing
Block #106,934,010
24 transactions · 23 stateful · 2026-09-22 03:58:55 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,010 · 24 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
1w02w13w24w35w46w510w011w112w213w314w415w516w622w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388ab72e…e6e6
0x34b655…2a6f
14 touches
21 conflicts
0x7462b8f2…6312
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 conflicts
0x4423a307…9f47
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 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
21 conflicts on slot 0x388ab72e91…70e6e6
Audit this contract →
← previous block·next block →recent activity