pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,673,005
← previous block
next block →
recent activity
Analyzing
Block #97,673,005
10 transactions · 10 stateful · 2026-08-20 16:35:21 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,673,005
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
execOrders
· blocks 1
#4
execOrders
· blocks 1
#5
execFwdPositionOpsV2
#7
setData
#8
claim
#9
0x59558d29
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4a95e21…8ec7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x2623ecd3…2b14
0x34b655…2a6f
2 touches
0 conflicts
0x5ac98a73…5f6a
0x34b655…2a6f
2 touches
0 conflicts
0x7265675e…d0d3
0x34b655…2a6f
2 touches
0 conflicts
0x9182cdc8…e2e5
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
0xb4a95e21a9…358ec7
Audit this contract →
← previous block
·
next block →
recent activity