← previous blocknext block →recent activity
Analyzing
Block #106,392,354
24 transactions · 24 stateful · 2026-09-20 06:31:42 UTC
Parallelism
54/100
Blocked
79%
Avg conflicts / tx
2.83
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,392,354 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w26w17w28w39w211w412w313w514w615w717w819w1021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ecffdb2…0a01
0x34b655…2a6f
14 touches
21 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
14 touches
21 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
12 touches
15 conflicts
0x364036f4…10de
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x48203298…65cb
0x34b655…2a6f
8 touches
6 conflicts
0x000bde1a…e123
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 0x2ecffdb210…300a01
Audit this contract →
← previous block·next block →recent activity