← previous blocknext block →recent activity
Analyzing
Block #106,385,976
19 transactions · 18 stateful · 2026-09-20 05:59:36 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,385,976 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w06w18w29w210w313w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
10 touches
10 conflicts
0xa96fec52…2ebd
0x34b655…2a6f
8 touches
6 conflicts
0x9fa1409b…0e55
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
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
10 conflicts on slot 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity