← previous blocknext block →recent activity
Analyzing
Block #106,457,538
22 transactions · 20 stateful · 2026-09-20 11:59:49 UTC
Parallelism
77/100
Blocked
60%
Avg conflicts / tx
1.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,457,538 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w09w210w311w312w413w015w117w119w221w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a6b4037…febd
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xac0b4a08…faae
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0x739cf558…6266
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
6 conflicts on slot 0x2a6b40371b…66febd
Audit this contract →
← previous block·next block →recent activity