← previous blocknext block →recent activity
Analyzing
Block #106,422,628
45 transactions · 32 stateful · 2026-09-20 09:04:03 UTC
Parallelism
87/100
Blocked
56%
Avg conflicts / tx
1.22
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,422,628 · 45 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
1w02w04w16w07w18w29w310w011w112w228w129w230w332w235w336w438w444w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xb6ed530c…d450
0x34b655…2a6f
12 touches
15 conflicts
0xf34199f9…a570
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x52e69143…95ad
0x065c9d…c394
10 touches
10 conflicts
0xce827910…ff22
0x065c9d…c394
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
15 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity