← previous blocknext block →recent activity
Analyzing
Block #106,953,444
22 transactions · 21 stateful · 2026-09-22 05:36:45 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,953,444 · 22 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
1w02w13w25w06w19w010w112w213w314w217w418w521w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37ad906a…ae75
0x34b655…2a6f
8 touches
6 conflicts
0xfba4b619…348a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x3e04662b…0da6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x53ca1284…cb2c
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 0x37ad906a14…7aae75
Audit this contract →
← previous block·next block →recent activity