← previous blocknext block →recent activity
Analyzing
Block #106,330,227
18 transactions · 18 stateful · 2026-09-20 01:19:02 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,330,227 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w17w08w09w310w411w514w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf10f9d72…32e0
0x34b655…2a6f
10 touches
10 conflicts
0xdbf974a4…b232
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8a872d05…dc87
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
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
10 conflicts on slot 0xf10f9d7273…9232e0
Audit this contract →
← previous block·next block →recent activity