pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,564,229
← previous block
next block →
recent activity
Analyzing
Block #84,564,229
10 transactions · 9 stateful · 2026-06-29 23:34:29 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,564,229
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0x6a43017d
#7
setData
#8
0x39435dac
· blocks 1
#5
0x0f6795d9
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfc4e5eab…639b
0x34b655…2a6f
4 touches
1 conflict
0x02c4bb0f…f2c8
0x34b655…2a6f
2 touches
0 conflicts
0x089552b1…a1cd
0x34b655…2a6f
2 touches
0 conflicts
0x1175233a…64e7
0x34b655…2a6f
2 touches
0 conflicts
0x1929338b…cd11
0x34b655…2a6f
2 touches
0 conflicts
0x2c15adb7…e65d
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:
Perpl
1 conflict on slot
0x97c6748621…2727fe
Audit this contract →
← previous block
·
next block →
recent activity