← previous blocknext block →recent activity
Analyzing
Block #106,565,595
22 transactions · 22 stateful · 2026-09-20 21:03:38 UTC
Parallelism
68/100
Blocked
64%
Avg conflicts / tx
1.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,565,595 · 22 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
1w02w03w14w15w26w18w29w310w413w114w215w416w517w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa00ca431…bd5c
0x34b655…2a6f
10 touches
10 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
8 touches
6 conflicts
0xac0b4a08…faae
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xa6464996…3af9
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
10 conflicts on slot 0xa00ca431b8…73bd5c
Audit this contract →
← previous block·next block →recent activity