pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,987,676
← previous block
next block →
recent activity
Analyzing
Block #97,987,676
13 transactions · 8 stateful · 2026-08-21 19:15:41 UTC
Parallelism
85
/100
Blocked
25
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,987,676
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
#2
0x7b84f330
· blocks 1
#3
execOrders
· blocks 1
#5
execPerpOps
#6
execPerpOps
#7
execFwdPositionOpsV2
#8
setData
#9
setData
#10
0x61d59c2d
#11
0x7b84f330
#4
execOrders
#12
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12e7c471…901c
0x34b655…2a6f
2 touches
0 conflicts
0x14cc77c7…69c4
0x34b655…2a6f
2 touches
0 conflicts
0x177e3941…97ae
0x34b655…2a6f
2 touches
0 conflicts
0x30908823…a62d
0x34b655…2a6f
2 touches
0 conflicts
0x3a874ce6…22d1
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