pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,743,218
← previous block
next block →
recent activity
Analyzing
Block #80,743,218
13 transactions · 13 stateful · 2026-06-12 06:44:20 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,743,218
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
0xed82b078
#5
0x98717539
#6
0x785f5745
· blocks 1
#7
0x3f5c179b
#8
updateDataFeedsValuesPartial
#9
0x6a2bab3c
#10
setData
#12
0xc7e3ec2c
#2
0x0c7abd22
#11
0x785f5745
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x00000000…0001
0xbab229…9388
4 touches
1 conflict
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0xffa41992…fd31
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
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
0x5860c4f397…270c39
Audit this contract →
← previous block
·
next block →
recent activity