← previous blocknext block →recent activity
Analyzing
Block #106,539,236
35 transactions · 30 stateful · 2026-09-20 18:50:59 UTC
Parallelism
66/100
Blocked
47%
Avg conflicts / tx
1.34
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,539,236 · 35 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w28w39w410w511w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xeb09bf17…4364
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x8ce695ab…a7c8
0x34b655…2a6f
8 touches
6 conflicts
0xa4279852…769b
0x34b655…2a6f
8 touches
6 conflicts
0xbaf6ed88…c179
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
28 conflicts on slot 0x735a86cd19…53b64d
Audit this contract →
← previous block·next block →recent activity