pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,999,141
← previous block
next block →
recent activity
Analyzing
Block #97,999,141
12 transactions · 12 stateful · 2026-08-21 20:13:32 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,999,141
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0x6ad2e98b
#3
execOrders
#4
0x59558d29
#5
execPerpOps
· blocks 1
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
setData
#6
execPerpOps
#11
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0aaaed20…6ab0
0x34b655…2a6f
2 touches
0 conflicts
0x18978822…2623
0x34b655…2a6f
2 touches
0 conflicts
0x2130a548…c1de
0x34b655…2a6f
2 touches
0 conflicts
0x2cef1eff…9f14
0x34b655…2a6f
2 touches
0 conflicts
0x4b67947a…c3bd
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