← previous blocknext block →recent activity
Analyzing
Block #106,199,503
38 transactions · 33 stateful · 2026-09-19 14:21:05 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.61
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,199,503 · 38 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
2w03w14w15w221w222w323w424w525w626w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff4ca89…6115
0x34b655…2a6f
12 touches
15 conflicts
0xed0c288a…471c
0x34b655…2a6f
12 touches
15 conflicts
0x83522595…9b28
0x34b655…2a6f
12 touches
15 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0x98568c43…ff4e
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
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
15 conflicts on slot 0x9ff4ca89cb…c96115
Audit this contract →
← previous block·next block →recent activity