pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,866,104
← previous block
next block →
recent activity
Analyzing
Block #75,866,104
11 transactions · 10 stateful · 2026-05-20 16:38:30 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,866,104
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
redeemDelegations
#3
0x62be7533
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
0x6df9e92b
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x75c3ab…4f0d
4 touches
1 conflict
0x5593214e…dfc1
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x5e1b1a…7777
4 touches
1 conflict
0x4d1acd7c…f345
0x5e1b1a…7777
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x75c3ab…4f0d
4 touches
1 conflict
0x5b9b10bf…b065
0x5afd3e…7620
2 touches
0 conflicts
0xdc0ce212…bb21
0x5afd3e…7620
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:
0x75c3ab75…ef4f0d
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity