pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,558,670
← previous block
next block →
recent activity
Analyzing
Block #84,558,670
10 transactions · 10 stateful · 2026-06-29 22:57:22 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,558,670
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
execOrders
· blocks 2
#6
setData
#7
cancelTournament
#5
execOrders
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x1ca44c02…4108
0x34b655…2a6f
4 touches
1 conflict
0x1f44bdf9…51aa
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x24227bc5…cb16
0x34b655…2a6f
4 touches
1 conflict
0x2c15adb7…e65d
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x56253387…ff0e
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x03fb27fddd…f00c06
Audit this contract →
← previous block
·
next block →
recent activity