pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,108,835
← previous block
next block →
recent activity
Analyzing
Block #84,108,835
13 transactions · 9 stateful · 2026-06-27 20:59:14 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,108,835
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xa96df62f
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
withdraw
#6
0xed82b078
#7
0x6a403a1a
#8
setData
#9
redeemDelegations
#10
0x39435dac
· blocks 1
#12
0xc7e3ec2c
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa80684c9…3948
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
0x06cef7b4…dee7
0x065c9d…c394
2 touches
0 conflicts
0x1b603aef…54cd
0x065c9d…c394
2 touches
0 conflicts
0xa992b02f…9f08
0x065c9d…c394
2 touches
0 conflicts
0x1cc848eb…5856
0x11ed3b…2c96
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
0xa80684c9ae…1b3948
Audit this contract →
← previous block
·
next block →
recent activity