← previous blocknext block →recent activity
Analyzing
Block #106,099,854
16 transactions · 16 stateful · 2026-09-19 05:59:35 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,099,854 · 16 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
1w02w13w24w08w19w211w312w413w014w115w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0xed506426…e6ad
0x34b655…2a6f
8 touches
6 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x6c6f37ba…c209
0x1b6862…e19c
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
6 conflicts on slot 0x85eb131679…60bb9e
Audit this contract →
← previous block·next block →recent activity