pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,327,774
← previous block
next block →
recent activity
Analyzing
Block #82,327,774
11 transactions · 8 stateful · 2026-06-19 14:45:57 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,327,774
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xb264ae19
· blocks 1
#4
0xab083028
#5
updateDataFeedsValuesPartial
#6
0x0c7abd22
#7
0x23afbff3
#8
setData
#9
0x57368ddf
#10
0xc7e3ec2c
#3
0xb264ae19
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x2c7e7448…9501
0x0000a8…8888
4 touches
1 conflict
0x92339d95…0801
0x0000a8…8888
4 touches
1 conflict
0x322266fd…529d
0x754704…b603
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0xb07a35ae…9f83
0x754704…b603
4 touches
1 conflict
0xd95b1a11…4e4d
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
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
0x99f666e3cf…76b2a2
Audit this contract →
← previous block
·
next block →
recent activity