pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,018,154
← previous block
next block →
recent activity
Analyzing
Block #84,018,154
14 transactions · 11 stateful · 2026-06-27 10:55:03 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,018,154
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
redeemDelegations
#4
0x0f6795d9
· blocks 1
#6
0x2a261d7a
#7
0xed82b078
#8
updateDataFeedsValuesPartial
#9
0x6a3fac7f
#10
0xe9316489
#11
setData
#12
execute
#13
0x39435dac
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2c7e7448…9500
0x0000a8…8888
2 touches
0 conflicts
0x2c7e7448…9501
0x0000a8…8888
2 touches
0 conflicts
0x5cbdceef…85ac
0x0000a8…8888
2 touches
0 conflicts
0x92339d95…0801
0x0000a8…8888
2 touches
0 conflicts
0x655be0b8…7e9e
0x1001ff…1001
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
0xffc2f21efe…ecb393
Audit this contract →
← previous block
·
next block →
recent activity