← previous blocknext block →recent activity
Analyzing
Block #106,053,727
23 transactions · 21 stateful · 2026-09-19 02:07:27 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,053,727 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w310w411w517w621w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd62f3741…b903
0x34b655…2a6f
14 touches
21 conflicts
0x837fb53e…b580
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
0x34b655…2a6f
8 touches
6 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
8 touches
6 conflicts
0x3dadb22d…64df
0x34b655…2a6f
8 touches
6 conflicts
0x14d1bf0e…e09c
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 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 0xd62f374157…55b903
Audit this contract →
← previous block·next block →recent activity