← previous blocknext block →recent activity
Analyzing
Block #106,575,861
34 transactions · 30 stateful · 2026-09-20 21:55:18 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,575,861 · 34 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
1w02w13w14w27w015w119w221w222w323w324w430w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07e1d521…fc32
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
8 touches
6 conflicts
0x9de5e190…269d
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x7c925651…2372
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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 0x07e1d52158…b8fc32
Audit this contract →
← previous block·next block →recent activity