← previous blocknext block →recent activity
Analyzing
Block #106,388,363
33 transactions · 31 stateful · 2026-09-20 06:11:37 UTC
Parallelism
61/100
Blocked
77%
Avg conflicts / tx
2.97
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,388,363 · 33 txs across 13 waves · depth 13
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
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w110w212w316w417w418w519w621w722w224w925w1027w1230w231w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x287ee53a…cb49
0x34b655…2a6f
14 touches
21 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
12 touches
15 conflicts
0x2c2761c0…476e
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0x0a6cb118…4ca5
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x038b9243…553d
0x34b655…2a6f
10 touches
10 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 0x287ee53a56…39cb49
Audit this contract →
← previous block·next block →recent activity