pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,074,213
← previous block
next block →
recent activity
Analyzing
Block #86,074,213
9 transactions · 8 stateful · 2026-07-06 23:20:07 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,074,213
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a4c389e
#8
setData
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x25957369…c648
0x34b655…2a6f
2 touches
0 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
2 touches
0 conflicts
0x608ebd53…deda
0x34b655…2a6f
2 touches
0 conflicts
0xac0b4a08…faae
0x34b655…2a6f
2 touches
0 conflicts
0xec0e0220…cb90
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x86cea35b12…8ebdff
Audit this contract →
← previous block
·
next block →
recent activity