pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,629,282
← previous block
next block →
recent activity
Analyzing
Block #83,629,282
9 transactions · 8 stateful · 2026-06-25 15:41:33 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
#83,629,282
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x39ecce49
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x6a3d4ca5
#7
setData
#8
execOrders
#3
0x39ecce49
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
0xc5d660d7…64e9
0xe1c8b7…3022
4 touches
1 conflict
0x12a9b76e…cb76
0x3bd359…433a
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x67d846dd…358c
0x506682…7777
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xf94c349c…d66d
0x9f3832…4ae4
4 touches
1 conflict
0xfce66a64…64e0
0x9f3832…4ae4
4 touches
1 conflict
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:
0xe1c8b733…e33022
1 conflict on slot
0xc5d660d76e…4164e9
Audit this contract →
← previous block
·
next block →
recent activity