pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,333,946
← previous block
next block →
recent activity
Analyzing
Block #98,333,946
13 transactions · 11 stateful · 2026-08-23 00:19:08 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,333,946
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a8a3cf4
#2
0x41a8f47c
· blocks 1
#3
0xab083028
#4
0x6ad2e98b
#5
0xab083028
#7
updatePrices
#8
updatePriceFeedsIfNecessary
#9
execFwdPositionOpsV2
#10
forward
#11
setData
#12
execOrders
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0xd421a518…8b5c
0x340143…768f
2 touches
0 conflicts
0xfd54ff1e…93c5
0x340143…768f
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
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:
0xbb3f3cb7…74e046
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity