pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,479,656
← previous block
next block →
recent activity
Analyzing
Block #81,479,656
10 transactions · 9 stateful · 2026-06-15 16:30:56 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,479,656
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#2
execute302
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updatePrices
#7
0x6a302938
#8
setData
#9
execOrders
#3
execute302
#6
0xaf47a8bb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xff3addfc…633e
0x6f4756…dd5b
4 touches
1 conflict
0xcc48f53c…ce04
0x9f3832…4ae4
2 touches
0 conflicts
0x00000000…0004
0x116377…f851
2 touches
0 conflicts
0x67d846dd…358c
0x1a48bd…7777
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:
0xe1c8b733…e33022
1 conflict on slot
0xa164d95170…fa1534
Audit this contract →
← previous block
·
next block →
recent activity