← previous blocknext block →recent activity
Analyzing
Block #106,388,180
34 transactions · 25 stateful · 2026-09-20 06:10:42 UTC
Parallelism
82/100
Blocked
52%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,388,180 · 34 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
2w05w17w08w19w210w311w417w018w119w221w225w326w427w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc9135baa…c4e9
0xd32edf…ff58
9 touches
10 conflicts
0x366a19b0…f065
0x34b655…2a6f
6 touches
3 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0x68292fe7…d918
0x34b655…2a6f
6 touches
3 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
6 touches
3 conflicts
0x9f63b181…919d
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
10 conflicts on slot 0x4681609fd4…e96493
Audit this contract →
← previous block·next block →recent activity