← previous blocknext block →recent activity
Analyzing
Block #106,568,026
23 transactions · 21 stateful · 2026-09-20 21:15:52 UTC
Parallelism
52/100
Blocked
57%
Avg conflicts / tx
1.22
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,568,026 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w08w111w312w213w415w516w617w718w819w920w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39c9325f…5a4e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x64f073d3…f738
0xd32edf…ff58
9 touches
10 conflicts
0xa242e227…2e45
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
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
10 conflicts on slot 0x39c9325f5a…be5a4e
Audit this contract →
← previous block·next block →recent activity