pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,622,809
← previous block
next block →
recent activity
Analyzing
Block #84,622,809
13 transactions · 10 stateful · 2026-06-30 06:04:45 UTC
Parallelism
62
/100
Blocked
40
%
Avg conflicts / tx
0.77
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,622,809
· 13 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
swap
· blocks 4
#6
0x39435dac
#7
forward
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x378a73…9b8b
#11
0x39435dac
#12
0x39435dac
#2
swap
· blocks 3
#3
swap
· blocks 2
#4
swap
· blocks 1
#5
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7332125a…5518
0x4917a5…1fe8
10 touches
10 conflicts
0x98c18a60…752f
0x000000…012a
10 touches
10 conflicts
0x00000000…0000
0xd5b70d…615b
10 touches
10 conflicts
0x00000000…0002
0xd5b70d…615b
10 touches
10 conflicts
0x00000000…0004
0xd5b70d…615b
10 touches
10 conflicts
0x00000000…0002
0x2d84d7…d457
10 touches
10 conflicts
0x00000000…0003
0x2d84d7…d457
10 touches
10 conflicts
0x00000000…0012
0x2d84d7…d457
10 touches
10 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:
0x4917a5ec…e81fe8
10 conflicts on slot
0x7332125a4e…825518
Audit this contract →
← previous block
·
next block →
recent activity