pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,250,953
← previous block
next block →
recent activity
Analyzing
Block #84,250,953
11 transactions · 11 stateful · 2026-06-28 12:45:41 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,250,953
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
executePacked
· blocks 1
#3
updatePrices
#5
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x0f6795d9
#10
0x39435dac
#4
0x6c05cd2b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcdba3b0…cfc2
0x3bd359…433a
4 touches
1 conflict
0xd352f775…a505
0x39b9e0…7777
4 touches
1 conflict
0x00000000…0000
0xf4e40a…28ea
4 touches
1 conflict
0x00000000…0002
0xf4e40a…28ea
4 touches
1 conflict
0x00000000…0003
0xf4e40a…28ea
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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:
Wrapped MON (WMON)
1 conflict on slot
0xfcdba3b0d5…f1cfc2
Audit this contract →
← previous block
·
next block →
recent activity