← previous blocknext block →recent activity
Analyzing
Block #106,470,917
41 transactions · 35 stateful · 2026-09-20 13:07:08 UTC
Parallelism
76/100
Blocked
54%
Avg conflicts / tx
1.37
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,470,917 · 41 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w416w117w418w120w021w122w023w125w228w229w332w634w835w938w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
14 touches
21 conflicts
0x24f7c4bd…9954
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c3
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x1c840894…764a
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity