pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,577,584
← previous block
next block →
recent activity
Analyzing
Block #83,577,584
11 transactions · 10 stateful · 2026-06-25 09:56:19 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
#83,577,584
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x785f5745
· blocks 1
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x6a3cfbbb
#8
execOrders
#9
execOrders
#10
0xc7e3ec2c
#4
0x785f5745
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0x5f037e8d…9f1b
0x0c65a0…0852
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x00df3324…9f35
0x34b655…2a6f
2 touches
0 conflicts
0x0c5c0224…826e
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:
0xbab2296c…069388
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity