← previous blocknext block →recent activity
Analyzing
Block #106,931,885
41 transactions · 38 stateful · 2026-09-22 03:48:13 UTC
Parallelism
61/100
Blocked
79%
Avg conflicts / tx
3.37
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,931,885 · 41 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w714w122w823w924w1025w1126w1227w1328w1429w1534w1036w1140w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04994ed2…9032
0x34b655…2a6f
20 touches
45 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
18 touches
36 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0x69168e33…6e1f
0x34b655…2a6f
16 touches
28 conflicts
0x2e6131b7…aed0
0xd32edf…ff58
15 touches
28 conflicts
0x4e7eb462…b2af
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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
45 conflicts on slot 0x04994ed232…129032
Audit this contract →
← previous block·next block →recent activity