← previous blocknext block →recent activity
Analyzing
Block #106,199,507
54 transactions · 51 stateful · 2026-09-19 14:21:06 UTC
Parallelism
63/100
Blocked
75%
Avg conflicts / tx
3.46
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #106,199,507 · 54 txs across 20 waves · depth 20
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
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w410w524w849w1151w1352w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98568c43…ff4e
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xd17580f9…ece1
0x754704…b603
14 touches
21 conflicts
0xffad2984…6add
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…002e
0x1b6862…e19c
12 touches
15 conflicts
0x69017fce…85c1
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
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
55 conflicts on slot 0x98568c43d7…70ff4e
Audit this contract →
← previous block·next block →recent activity