← previous blocknext block →recent activity
Analyzing
Block #106,916,333
21 transactions · 20 stateful · 2026-09-22 02:29:57 UTC
Parallelism
57/100
Blocked
55%
Avg conflicts / tx
1.48
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,916,333 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w28w39w410w411w512w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
12 touches
15 conflicts
0x69411fb3…e36d
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x825865a0…b736
0x34b655…2a6f
10 touches
10 conflicts
0xfc906557…ae7f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0d5c1721…e4b5
0x34b655…2a6f
4 touches
1 conflict
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 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity