pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,949,166
← previous block
next block →
recent activity
Analyzing
Block #75,949,166
11 transactions · 11 stateful · 2026-05-21 01:51:19 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,949,166
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0x98717539
#4
redeemDelegations
#5
redeemDelegations
#6
updatePosition
#7
updateDataFeedsValuesPartial
#8
updateTemporalNumericValuesV1
#9
setData
#10
0x39435dac
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f5a2e2b…65f1
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9355
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9356
0x1d1325…2305
4 touches
1 conflict
0x4b61ebf9…49cb
0x065c9d…c394
4 touches
1 conflict
0xa605468c…1bfc
0x1d1325…2305
4 touches
1 conflict
0xc8525006…2b45
0x1d1325…2305
4 touches
1 conflict
0x1fff6dcb…b3f4
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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:
0x1d1325c2…f62305
1 conflict on slot
0x1f5a2e2bdd…b665f1
Audit this contract →
← previous block
·
next block →
recent activity