← previous blocknext block →recent activity
Analyzing
Block #106,367,011
31 transactions · 29 stateful · 2026-09-20 04:24:09 UTC
Parallelism
74/100
Blocked
72%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,367,011 · 31 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
1w03w14w25w36w415w516w617w218w319w320w422w223w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99ccc63c…6624
0x34b655…2a6f
12 touches
15 conflicts
0x5d1ac445…5233
0x34b655…2a6f
10 touches
10 conflicts
0x7ca1d988…b963
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xab2a87f1…eafd
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
15 conflicts on slot 0x99ccc63cf7…146624
Audit this contract →
← previous block·next block →recent activity