← previous blocknext block →recent activity
Analyzing
Block #106,542,706
31 transactions · 31 stateful · 2026-09-20 19:08:26 UTC
Parallelism
61/100
Blocked
58%
Avg conflicts / tx
2
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,542,706 · 31 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
1w02w13w24w35w36w47w58w621w726w627w728w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
14 touches
21 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x4b915012…df64
0x34b655…2a6f
12 touches
15 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
12 touches
15 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
8 touches
6 conflicts
0xc9a8c9ab…cd37
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
21 conflicts on slot 0x735a86cd19…53b64d
Audit this contract →
← previous block·next block →recent activity