pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,287,257
← previous block
next block →
recent activity
Analyzing
Block #98,287,257
13 transactions · 12 stateful · 2026-08-22 20:24:11 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,287,257
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xa96df62f
#3
0x7b84f330
· blocks 1
#4
matchOrders
#5
0xab083028
#6
execOrders
#7
0x59558d29
#8
execFwdPositionOpsV2
#9
commit
#10
setData
#11
execOrders
#12
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2c0f392b…d071
0x34b655…2a6f
2 touches
0 conflicts
0x54907f2c…4a40
0x34b655…2a6f
2 touches
0 conflicts
0x67a56c8b…f955
0x34b655…2a6f
2 touches
0 conflicts
0x9d9f3717…44e7
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:
0x34014398…d1768f
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity