← previous blocknext block →recent activity
Analyzing
Block #106,471,340
30 transactions · 28 stateful · 2026-09-20 13:09:16 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.77
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,471,340 · 30 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
1w02w13w24w36w07w18w29w310w411w512w623w826w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c840894…764a
0x34b655…2a6f
16 touches
28 conflicts
0x85676476…abed
0x34b655…2a6f
12 touches
15 conflicts
0xc389d1ff…6a00
0x34b655…2a6f
10 touches
10 conflicts
0x94e7f277…471b
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xd1480c90…ae08
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x06d1dd11…9502
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 0x1c84089465…17764a
Audit this contract →
← previous block·next block →recent activity