pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,905,652
← previous block
next block →
recent activity
Analyzing
Block #74,905,652
8 transactions · 7 stateful · 2026-05-16 05:37:04 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,905,652
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
redeemDelegations
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updatePosition
#4
0xed82b078
#5
0x6a0802f8
#6
setData
#7
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xe3d17f…3f96
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x37e1be01…6f19
0x54cd53…9e7d
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x0c586972…3d5e
0x6657d1…8ccc
2 touches
0 conflicts
0x0ef9f8af…dc15
0x6657d1…8ccc
2 touches
0 conflicts
0x0f0ee975…de81
0x6657d1…8ccc
2 touches
0 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:
0xe3d17f49…d93f96
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity