← previous blocknext block →recent activity
Analyzing
Block #106,420,043
25 transactions · 23 stateful · 2026-09-20 08:51:03 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,420,043 · 25 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
1w02w13w24w35w36w47w58w612w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cab9ef4…f849
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x7cd9fd28…a158
0x34b655…2a6f
8 touches
6 conflicts
0x48a081a8…f441
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x6d955786…1327
0x34b655…2a6f
8 touches
6 conflicts
0x05b1f4af…b126
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 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 0x6cab9ef455…bff849
Audit this contract →
← previous block·next block →recent activity