← previous blocknext block →recent activity
Analyzing
Block #106,541,811
15 transactions · 13 stateful · 2026-09-20 19:03:56 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,541,811 · 15 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
1w02w13w24w35w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbf974a4…b232
0x34b655…2a6f
8 touches
6 conflicts
0xa08efe82…5d69
0x34b655…2a6f
8 touches
6 conflicts
0x4b723405…a8c5
0xd32edf…ff58
7 touches
6 conflicts
0xb2560305…f27d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xd6071d1d…496b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xad862891…5d02
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 0xdbf974a4cf…a9b232
Audit this contract →
← previous block·next block →recent activity