← previous blocknext block →recent activity
Analyzing
Block #106,363,072
20 transactions · 19 stateful · 2026-09-20 04:04:20 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,363,072 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72a1afae…0b1c
0x34b655…2a6f
10 touches
10 conflicts
0xc8cb0701…3926
0x34b655…2a6f
8 touches
6 conflicts
0x5d1ac445…5233
0x34b655…2a6f
8 touches
6 conflicts
0x23592ab4…9ba8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
10 conflicts on slot 0x72a1afae64…930b1c
Audit this contract →
← previous block·next block →recent activity