← previous blocknext block →recent activity
Analyzing
Block #106,569,147
29 transactions · 24 stateful · 2026-09-20 21:21:30 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
1.28
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,569,147 · 29 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w29w310w411w515w321w422w523w624w625w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe04cc2…7148
0x34b655…2a6f
14 touches
21 conflicts
0x3cf50d44…961b
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x20b1228b…2487
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x0e3b59e9…d9d0
0x34b655…2a6f
6 touches
3 conflicts
0xe8e4663b…2783
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
21 conflicts on slot 0x5fe04cc2ff…a97148
Audit this contract →
← previous block·next block →recent activity