pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,473,531
← previous block
next block →
recent activity
Analyzing
Block #98,473,531
9 transactions · 8 stateful · 2026-08-23 12:01:44 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,473,531
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
0x3f5c179b
#7
0x6a8ae1a0
#8
setData
#2
execOrders
· blocks 1
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0f8965bb…e238
0x34b655…2a6f
2 touches
0 conflicts
0x1d48c0e2…b62e
0x34b655…2a6f
2 touches
0 conflicts
0x35b29270…6558
0x34b655…2a6f
2 touches
0 conflicts
0x35e29426…121c
0x34b655…2a6f
2 touches
0 conflicts
0x37c0660b…e0bf
0x34b655…2a6f
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:
Perpl
3 conflicts on slot
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity