← previous blocknext block →recent activity
Analyzing
Block #106,215,521
31 transactions · 28 stateful · 2026-09-19 15:41:45 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,215,521 · 31 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
1w02w13w24w35w46w07w18w311w412w013w116w017w118w521w524w425w626w027w128w229w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b501ca7…3852
0x34b655…2a6f
8 touches
6 conflicts
0x47facc73…35bd
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x6d43ee99…bdda
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 0x1b501ca794…ee3852
Audit this contract →
← previous block·next block →recent activity