pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,818,326
← previous block
next block →
recent activity
Analyzing
Block #97,818,326
10 transactions · 9 stateful · 2026-08-21 04:50:49 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,818,326
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
0x5acec890
· blocks 2
#5
forward
#6
execFwdPositionOpsV2
#7
setData
#8
0x59558d29
#4
0x0c7abd22
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f9d2897…6a3f
0x34b655…2a6f
6 touches
3 conflicts
0x6a2dee17…49e4
0x34b655…2a6f
4 touches
1 conflict
0xd080c1f8…8b0c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
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
3 conflicts on slot
0x3f9d2897b8…aa6a3f
Audit this contract →
← previous block
·
next block →
recent activity