pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,478,759
← previous block
next block →
recent activity
Analyzing
Block #81,478,759
12 transactions · 12 stateful · 2026-06-15 16:24:56 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,478,759
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xc1274a2e
· blocks 1
#2
batchUpdate
· blocks 1
#5
batchUpdate
#6
updateDataFeedsValuesPartial
#7
0x98717539
#8
0x0c7abd22
#9
forward
#10
setData
#11
execOrders
#3
batchUpdate
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7a3d42d…e766
0x40c49f…2af0
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x678637c5…90f8
0x065c9d…c394
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
2 touches
0 conflicts
0xfb630be8…f332
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0001
0x453805…c7fd
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
0xd7a3d42dc0…66e766
Audit this contract →
← previous block
·
next block →
recent activity