pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,031,835
← previous block
next block →
recent activity
Analyzing
Block #84,031,835
15 transactions · 13 stateful · 2026-06-27 12:26:09 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,031,835
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
redeemDelegations
#3
execFwdPositionOps
#4
0x0c7abd22
· blocks 1
#5
0x9e76c652
#7
0xed82b078
#8
execFwdPositionOps
#9
0x6a3fc1d9
#10
setData
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2df73438…704d
0x386489…7508
2 touches
0 conflicts
0x31e052ed…3133
0x386489…7508
2 touches
0 conflicts
0x36638c1c…d348
0x3bd359…433a
2 touches
0 conflicts
0x544ac270…ab6b
0x3bd359…433a
2 touches
0 conflicts
0x57beaff2…7636
0x3ef3d8…d9ae
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity