← previous blocknext block →recent activity
Analyzing
Block #106,186,671
24 transactions · 23 stateful · 2026-09-19 13:16:30 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,186,671 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w17w18w211w212w313w315w316w317w418w519w123w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b713a9f…c0be
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x94dabb65…43a3
0x34b655…2a6f
8 touches
6 conflicts
0xd62f3741…b903
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
15 conflicts on slot 0x7b713a9fb6…cdc0be
Audit this contract →
← previous block·next block →recent activity