pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,546,934
← previous block
next block →
recent activity
Analyzing
Block #84,546,934
12 transactions · 10 stateful · 2026-06-29 21:39:09 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,546,934
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
_makeSwaps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
0x5bf9264c
#6
0x5bf9264c
#7
0x0f6795d9
#8
0x6a42e675
#9
setData
#10
0x39435dac
#11
0xc7e3ec2c
#2
0x6ad2e98b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5774710f…aa8e
0x851145…3f07
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0xc00fc7fc…f47e
0x01bff4…1071
2 touches
0 conflicts
0x00000000…0001
0x0cc02c…75b2
2 touches
0 conflicts
0x00000000…0006
0x0cc02c…75b2
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:
0x851145ea…9f3f07
1 conflict on slot
0x5774710f19…30aa8e
Audit this contract →
← previous block
·
next block →
recent activity