← previous blocknext block →recent activity
Analyzing
Block #106,917,454
18 transactions · 17 stateful · 2026-09-22 02:35:35 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
1.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,917,454 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w110w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x251ee419…4404
0x34b655…2a6f
14 touches
21 conflicts
0x70986451…c6bd
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x91220b8f…7a06
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 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 0x251ee41913…494404
Audit this contract →
← previous block·next block →recent activity