pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,202,385
← previous block
next block →
recent activity
Analyzing
Block #81,202,385
11 transactions · 7 stateful · 2026-06-14 09:44:21 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,202,385
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x6a2e786c
#7
0x5fff4c…ba10
#8
0xca918b…4f71
#9
0xad39e5…b7f7
#10
0x22c5d0…bc45
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x01638b8a…1674
0x40c49f…2af0
2 touches
0 conflicts
0x4c13c80e…d834
0x40c49f…2af0
2 touches
0 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity