← previous blocknext block →recent activity
Analyzing
Block #106,917,254
31 transactions · 31 stateful · 2026-09-22 02:34:35 UTC
Parallelism
42/100
Blocked
68%
Avg conflicts / tx
3.03
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,917,254 · 31 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
1w02w13w04w15w26w37w48w59w610w711w812w913w1014w1115w1216w1317w1418w1519w1620w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94e7f277…471b
0x34b655…2a6f
22 touches
55 conflicts
0xccebf5c5…8758
0x34b655…2a6f
20 touches
45 conflicts
0xe06d2b07…cdd0
0x34b655…2a6f
20 touches
45 conflicts
0xba1edffb…323e
0x34b655…2a6f
18 touches
36 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0xa0998a89…1f5a
0x34b655…2a6f
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1ee57dc9…5a51
0x34b655…2a6f
4 touches
1 conflict
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 0x94e7f27794…c6471b
Audit this contract →
← previous block·next block →recent activity