← previous blocknext block →recent activity
Analyzing
Block #106,252,569
25 transactions · 21 stateful · 2026-09-19 18:48:15 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,252,569 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w210w011w114w115w016w117w218w319w420w522w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59ec0dd4…543c
0x34b655…2a6f
10 touches
10 conflicts
0x3ec53e25…569f
0x34b655…2a6f
8 touches
6 conflicts
0x6b267bdf…b173
0x34b655…2a6f
8 touches
6 conflicts
0xd911522b…e960
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xd2f1ae13…f43c
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x5717771c…45ed
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 0x59ec0dd4a7…2d543c
Audit this contract →
← previous block·next block →recent activity