pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,254,809
← previous block
next block →
recent activity
Analyzing
Block #84,254,809
11 transactions · 9 stateful · 2026-06-28 13:11:20 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,254,809
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
forward
#7
updateTemporalNumericValuesV1
#8
setData
#9
0x39435dac
#10
0x50a0b275
#2
0xaf5e395a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f1434d4…1ce1
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x2d59fc…cd50
4 touches
1 conflict
0x00000000…0004
0x2d59fc…cd50
4 touches
1 conflict
0x3f1434d4…1ce1
0x11ed3b…2c96
4 touches
1 conflict
0x00000000…0000
0x2d59fc…cd50
4 touches
1 conflict
0x21c137b8…3a77
0x3bd359…433a
2 touches
0 conflicts
0xfe3bddd2…8b48
0x3bd359…433a
2 touches
0 conflicts
0x0820c477…a011
0x402807…5159
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
0x3f1434d4b2…9e1ce1
Audit this contract →
← previous block
·
next block →
recent activity