← previous blocknext block →recent activity
Analyzing
Block #106,100,427
21 transactions · 20 stateful · 2026-09-19 06:02:28 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,100,427 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w19w310w412w215w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a2896a0…2a0a
0x34b655…2a6f
14 touches
21 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
10 touches
10 conflicts
0x0c0ca07f…b78d
0x34b655…2a6f
10 touches
10 conflicts
0xb110d1eb…61bc
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0xaffceee4…7d2c
0x34b655…2a6f
4 touches
1 conflict
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 0x2a2896a01b…cc2a0a
Audit this contract →
← previous block·next block →recent activity