← previous blocknext block →recent activity
Analyzing
Block #106,915,934
21 transactions · 21 stateful · 2026-09-22 02:27:56 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,915,934 · 21 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
1w02w14w19w010w111w212w313w414w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1b79aeb…a0d2
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x206f4379…e08a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x607e2ee6…759a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xd1b79aeb2c…90a0d2
Audit this contract →
← previous block·next block →recent activity