pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,496,638
← previous block
next block →
recent activity
Analyzing
Block #84,496,638
10 transactions · 9 stateful · 2026-06-29 16:03:15 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,496,638
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x5a5d9a99
#4
0x0f6795d9
#5
0x0f6795d9
· blocks 1
#6
0xed82b078
#7
0x6a4297bb
#8
setData
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeebaa043…0d3c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7e647ee2…c22b
0x065c9d…c394
2 touches
0 conflicts
0xbb56c92d…76fb
0x065c9d…c394
2 touches
0 conflicts
0xdb5106c7…ebc1
0x065c9d…c394
2 touches
0 conflicts
0xf2905b4e…aa7c
0x065c9d…c394
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
0xeebaa04358…cc0d3c
Audit this contract →
← previous block
·
next block →
recent activity