← previous blocknext block →recent activity
Analyzing
Block #106,362,887
31 transactions · 31 stateful · 2026-09-20 04:03:24 UTC
Parallelism
48/100
Blocked
58%
Avg conflicts / tx
3.71
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,362,887 · 31 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w39w410w111w517w618w719w820w921w1022w1123w1224w1325w1426w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6d2da5f…9e78
0x34b655…2a6f
22 touches
55 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
20 touches
45 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xa711e6b5…6a3a
0x34b655…2a6f
14 touches
21 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x574628e9…dcc3
0x34b655…2a6f
12 touches
15 conflicts
0xac0b4a08…faae
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0xf6d2da5f70…b69e78
Audit this contract →
← previous block·next block →recent activity