pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,704,190
← previous block
next block →
recent activity
Analyzing
Block #80,704,190
12 transactions · 6 stateful · 2026-06-12 02:24:00 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,704,190
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
0x98717539
#9
0x98717539
#10
0x3f5c179b
#11
setData
#3
updatePrices
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
0x00000000…0002
0x6fae99…a56d
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x55579de4…0ccf
0x34b655…2a6f
2 touches
0 conflicts
0x8f4baaf9…5417
0x34b655…2a6f
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:
0x6fae9933…7ba56d
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity