← previous blocknext block →recent activity
Analyzing
Block #106,952,155
34 transactions · 25 stateful · 2026-09-22 05:30:15 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,952,155 · 34 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w09w010w013w015w118w120w221w122w023w124w225w328w229w330w132w133w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a5dca8…326a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xaa361252…1221
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
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
6 conflicts on slot 0x34a5dca8c9…91326a
Audit this contract →
← previous block·next block →recent activity