← previous blocknext block →recent activity
Analyzing
Block #106,950,422
10 transactions · 10 stateful · 2026-09-22 05:21:32 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,950,422 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc953c572…34b1
0x34b655…2a6f
4 touches
1 conflict
0xe4085f26…0cd8
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x46483cb1…e7ca
0x34b655…2a6f
2 touches
0 conflicts
0x70986451…c6bd
0x34b655…2a6f
2 touches
0 conflicts
0x8e2aea13…258c
0x34b655…2a6f
2 touches
0 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc953c57268…e534b1
Audit this contract →
← previous block·next block →recent activity