← previous blocknext block →recent activity
Analyzing
Block #106,931,366
34 transactions · 33 stateful · 2026-09-22 03:45:37 UTC
Parallelism
47/100
Blocked
76%
Avg conflicts / tx
2.76
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,931,366 · 34 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w612w713w814w915w1016w1117w1218w1319w521w1329w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23769ebc…c8ed
0x34b655…2a6f
20 touches
45 conflicts
0xc924ae2d…6941
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0xa9988419…9f45
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x715eeec8…5664
0x34b655…2a6f
12 touches
15 conflicts
0x721c4bf6…290c
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
45 conflicts on slot 0x23769ebc9a…0ec8ed
Audit this contract →
← previous block·next block →recent activity