← previous blocknext block →recent activity
Analyzing
Block #106,952,916
39 transactions · 37 stateful · 2026-09-22 05:34:05 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.74
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,952,916 · 39 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w08w09w110w211w312w419w521w625w129w130w731w832w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x267cce70…8ae3
0x34b655…2a6f
12 touches
15 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x5508eda6…cbea
0x34b655…2a6f
10 touches
10 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x8f18c248…9da5
0x34b655…2a6f
10 touches
10 conflicts
0x8aa821c7…a28d
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 0x267cce70eb…608ae3
Audit this contract →
← previous block·next block →recent activity