pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,724,459
← previous block
next block →
recent activity
Analyzing
Block #85,724,459
15 transactions · 7 stateful · 2026-07-05 08:28:32 UTC
Parallelism
87
/100
Blocked
14
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,724,459
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf5e395a
· blocks 1
#2
0x50a0b275
#4
____MEV_X____Ga543
#5
dagSwapByOrderId
#6
0x13572d0b
#7
____MEV_X____Ga543
#8
main_all
#9
main_all
#10
updateDataFeedsValuesPartial
#11
setData
#12
0x62be7533
#13
batchUpdate
#14
execOrders
#3
0x719d975a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0001
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0003
0x0d73bf…be07
4 touches
1 conflict
0xff393f19…4dd2
0x0a3323…0a3c
4 touches
1 conflict
0x3df7769a…5d17
0x3bd359…433a
4 touches
1 conflict
0x5b4cd072…c461
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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:
0x0d73bf86…a6be07
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity