← previous blocknext block →recent activity
Analyzing
Block #106,552,471
19 transactions · 19 stateful · 2026-09-20 19:57:35 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,552,471 · 19 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
1w02w13w27w08w19w010w112w213w314w415w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2592310e…03a5
0x34b655…2a6f
12 touches
15 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
10 touches
10 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x5a3732cb…edb1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x4be9812b…48a9
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
15 conflicts on slot 0x2592310e8c…6103a5
Audit this contract →
← previous block·next block →recent activity