← previous blocknext block →recent activity
Analyzing
Block #101,065,219
36 transactions · 33 stateful · 2026-09-01 14:24:28 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
2.03
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #101,065,219 · 36 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w09w010w111w314w015w117w421w222w526w127w628w729w830w931w1032w1133w1234w1335w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x7dd96c96…7335
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xe483d4e3…e52b
0x1b6862…e19c
6 touches
3 conflicts
0x68531239…e9a3
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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity