pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,019,523
← previous block
next block →
recent activity
Analyzing
Block #82,019,523
13 transactions · 8 stateful · 2026-06-18 04:30:10 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,019,523
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
batchCancelOrders
#6
execute
· blocks 1
#8
setData
#9
0x3aaee2…a3aa
#10
0x2c84a5…387a
#11
execOrders
#12
0xc7e3ec2c
#7
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x771a3650…01cd
0x3bd359…433a
4 touches
1 conflict
0x797464db…e15a
0x788571…8888
4 touches
1 conflict
0xa743c8dd…ebf2
0x788571…8888
4 touches
1 conflict
0x00000000…0000
0x24b18e…3301
4 touches
1 conflict
0x00000000…0001
0x24b18e…3301
4 touches
1 conflict
0x40faf0d5…5372
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
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
0x771a36505f…3f01cd
Audit this contract →
← previous block
·
next block →
recent activity