pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,607,731
← previous block
next block →
recent activity
Analyzing
Block #84,607,731
10 transactions · 9 stateful · 2026-06-30 04:24:28 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,607,731
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0x5bf9264c
#5
0x0f6795d9
#6
setData
#7
0x34653439
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x6a53b1c0…c3f2
0x34b655…2a6f
4 touches
1 conflict
0x7425a853…a582
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x8624277f…4b59
0x34b655…2a6f
4 touches
1 conflict
0x8fcf2308…746e
0x34b655…2a6f
4 touches
1 conflict
0x9c8a3533…a581
0x34b655…2a6f
4 touches
1 conflict
0xcfe15fba…4f97
0x34b655…2a6f
4 touches
1 conflict
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
0xe4af4c87c3…c59964
Audit this contract →
← previous block
·
next block →
recent activity