pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,480,882
← previous block
next block →
recent activity
Analyzing
Block #81,480,882
10 transactions · 8 stateful · 2026-06-15 16:39:08 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,480,882
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
batchCancelOrders
#2
batchUpdate
· blocks 1
#3
0xab083028
#5
batchUpdate
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#4
0xed82b078
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48acfd83…7ef0
0x40c49f…2af0
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x19e060dd…3a59
0x065c9d…c394
2 touches
0 conflicts
0x3cf568e8…269e
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x9d3f2124…725b
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
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:
0x40c49f17…d22af0
1 conflict on slot
0x48acfd8394…2b7ef0
Audit this contract →
← previous block
·
next block →
recent activity