← previous blocknext block →recent activity
Analyzing
Block #106,366,895
25 transactions · 23 stateful · 2026-09-20 04:23:34 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,366,895 · 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
1w02w13w24w28w011w314w316w417w518w619w723w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x760fc6c3…71f9
0x34b655…2a6f
16 touches
28 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
12 touches
15 conflicts
0x9b7187dd…3085
0x34b655…2a6f
10 touches
10 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x1244b105…8e9b
0x34b655…2a6f
6 touches
3 conflicts
0x2c2761c0…476e
0x34b655…2a6f
6 touches
3 conflicts
0xb9b077a8…e029
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
28 conflicts on slot 0x760fc6c389…7b71f9
Audit this contract →
← previous block·next block →recent activity