pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,618,316
← previous block
next block →
recent activity
Analyzing
Block #81,618,316
13 transactions · 9 stateful · 2026-06-16 07:54:30 UTC
Parallelism
85
/100
Blocked
22
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,618,316
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updatePrices
· blocks 1
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
0x6a3101ae
#9
setData
#11
forward
#12
forward
#4
updatePrices
#10
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb4c35fcd…43ae
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x89750670…2dea
0xa6afd3…d132
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
2 touches
0 conflicts
0xa4e3b3b1…0911
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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: Market-WETH/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity