pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,441,071
← previous block
next block →
recent activity
Analyzing
Block #98,441,071
16 transactions · 12 stateful · 2026-08-23 09:18:04 UTC
Parallelism
81
/100
Blocked
17
%
Avg conflicts / tx
0.19
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,441,071
· 16 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a8abb44
#2
0xab083028
#3
0x59558d29
#4
updatePrices
· blocks 2
#7
0x5de3085d
#8
execute
#9
withdraw
#10
0x3f5c179b
#11
0x9e76c652
#12
execFwdPositionOpsV2
#13
0x6a8abb44
#14
0x6a8abb44
#15
setData
#5
updatePrices
· blocks 1
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0004
0x65d862…09f4
2 touches
0 conflicts
0x00000000…0005
0x65d862…09f4
2 touches
0 conflicts
0x00000000…0006
0x65d862…09f4
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
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity