← previous blocknext block →recent activity
Analyzing
Block #106,931,353
33 transactions · 33 stateful · 2026-09-22 03:45:33 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
1.48
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,931,353 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w28w29w310w416w417w519w721w922w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f967fa7…2e16
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0xeb3f4bff…e791
0x34b655…2a6f
12 touches
15 conflicts
0x704a8131…bbe8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x9b334941…fddf
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x7f967fa7d8…652e16
Audit this contract →
← previous block·next block →recent activity