← previous blocknext block →recent activity
Analyzing
Block #106,426,207
43 transactions · 41 stateful · 2026-09-20 09:22:04 UTC
Parallelism
65/100
Blocked
80%
Avg conflicts / tx
3.72
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,426,207 · 43 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w616w117w518w621w723w724w825w926w1027w1128w1229w1330w1438w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd563f3a1…94b1
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xb25352df…f9e9
0x34b655…2a6f
16 touches
28 conflicts
0x9368aa25…bf30
0xd32edf…ff58
15 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0xfa324e43…8897
0x1b6862…e19c
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
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
45 conflicts on slot 0xd563f3a18c…f494b1
Audit this contract →
← previous block·next block →recent activity