← previous blocknext block →recent activity
Analyzing
Block #106,394,759
41 transactions · 38 stateful · 2026-09-20 06:43:49 UTC
Parallelism
68/100
Blocked
71%
Avg conflicts / tx
2.85
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,394,759 · 41 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
1w02w13w24w35w46w57w68w79w811w115w323w326w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b53436c…2ec3
0x34b655…2a6f
18 touches
36 conflicts
0xe4102b6c…2a51
0x34b655…2a6f
18 touches
36 conflicts
0x3f28a8a2…a59a
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…001a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002a
0x1b6862…e19c
14 touches
21 conflicts
0xd59f6ed1…03e6
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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
36 conflicts on slot 0x3b53436c6f…c62ec3
Audit this contract →
← previous block·next block →recent activity