← previous blocknext block →recent activity
Analyzing
Block #106,809,923
29 transactions · 29 stateful · 2026-09-21 17:34:20 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.69
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,809,923 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w27w211w312w415w516w617w321w728w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x981935b7…709d
0x34b655…2a6f
12 touches
15 conflicts
0xdf6b3ac1…433c
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x928d6b23…5370
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 0x981935b7b9…9e709d
Audit this contract →
← previous block·next block →recent activity