← previous blocknext block →recent activity
Analyzing
Block #106,420,169
24 transactions · 21 stateful · 2026-09-20 08:51:41 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,420,169 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w110w114w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x31d88d27…7617
0x34b655…2a6f
10 touches
10 conflicts
0x012ce12a…6de3
0x34b655…2a6f
10 touches
10 conflicts
0x888660ec…c3eb
0x34b655…2a6f
10 touches
10 conflicts
0x4e9d7bb8…cc95
0x34b655…2a6f
8 touches
6 conflicts
0x051ecd30…f7e7
0x34b655…2a6f
8 touches
6 conflicts
0xebf19faa…72cb
0x34b655…2a6f
8 touches
6 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity