pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,537,732
← previous block
next block →
recent activity
Analyzing
Block #84,537,732
9 transactions · 9 stateful · 2026-06-29 20:37:18 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,537,732
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x1094dc9f
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x6a42d7f5
#7
setData
#8
0x39435dac
#2
0x719d975a
· blocks 1
#3
executePacked
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcdba3b0…cfc2
0x3bd359…433a
4 touches
1 conflict
0xfe3bddd2…8b48
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
0xc0ad7883…c2ab
0x3bd359…433a
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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