pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,536,049
← previous block
next block →
recent activity
Analyzing
Block #97,536,049
13 transactions · 8 stateful · 2026-08-20 04:56:30 UTC
Parallelism
77
/100
Blocked
25
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,536,049
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
#3
updatePrices
· blocks 2
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
0xab083028
#10
updateDataFeedsValuesPartial
#11
setData
#12
0xb9df83…69d8
#4
updatePrices
· blocks 1
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x13956008…a919
0x065c9d…c394
2 touches
0 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
2 touches
0 conflicts
0xf963b7ae…bb8b
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
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:
0x103de0b5…25bb55
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity