← previous blocknext block →recent activity
Analyzing
Block #106,380,641
25 transactions · 23 stateful · 2026-09-20 05:32:45 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.64
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,380,641 · 25 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
1w02w13w26w07w08w111w013w314w416w117w418w519w520w621w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1e4ade9…32de
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xb9b077a8…e029
0x34b655…2a6f
8 touches
6 conflicts
0x362ac6f5…7b54
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
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 0xb1e4ade94a…d132de
Audit this contract →
← previous block·next block →recent activity