← previous blocknext block →recent activity
Analyzing
Block #106,163,686
30 transactions · 27 stateful · 2026-09-19 11:20:50 UTC
Parallelism
63/100
Blocked
63%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,163,686 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w37w410w511w613w117w218w819w920w321w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9430e759…86df
0x34b655…2a6f
16 touches
28 conflicts
0x222277a8…9034
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xf5d9f22d…e99f
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x5060cdde…445d
0x34b655…2a6f
8 touches
6 conflicts
0x546c8ed1…6a43
0x34b655…2a6f
8 touches
6 conflicts
0x673a703c…6433
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x9430e759ab…3f86df
Audit this contract →
← previous block·next block →recent activity