← previous blocknext block →recent activity
Analyzing
Block #106,950,246
34 transactions · 32 stateful · 2026-09-22 05:20:39 UTC
Parallelism
62/100
Blocked
69%
Avg conflicts / tx
2.24
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,950,246 · 34 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w36w49w413w514w615w716w819w520w621w124w425w926w1027w1128w1233w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd34797cc…fae9
0x34b655…2a6f
16 touches
28 conflicts
0xc953c572…34b1
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x34a5dca8…326a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1f396cee…862f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
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
28 conflicts on slot 0xd34797cc5c…18fae9
Audit this contract →
← previous block·next block →recent activity