← previous blocknext block →recent activity
Analyzing
Block #106,922,195
23 transactions · 21 stateful · 2026-09-22 02:59:27 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
1.52
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,922,195 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w29w010w112w213w314w316w417w518w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b696fc8…c909
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0x5b696fc830…8dc909
Audit this contract →
← previous block·next block →recent activity