pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,740,381
← previous block
next block →
recent activity
Analyzing
Block #98,740,381
12 transactions · 10 stateful · 2026-08-24 11:00:09 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,740,381
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0x59558d29
#4
0x000000b2
#5
0x3f5c179b
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0x6a8c24b0
#9
setData
#10
0x000000b2
#11
execOrders
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x02e940c4…4d93
0x34b655…2a6f
2 touches
0 conflicts
0x0547420b…fc46
0x34b655…2a6f
2 touches
0 conflicts
0x0d364226…1009
0x34b655…2a6f
2 touches
0 conflicts
0x0d63ff4f…4f9a
0x34b655…2a6f
2 touches
0 conflicts
0x29cac3f0…d958
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
1 conflict on slot
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity