pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,898,345
← previous block
next block →
recent activity
Analyzing
Block #97,898,345
11 transactions · 11 stateful · 2026-08-21 11:41:11 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,898,345
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0xab083028
#3
0x3f5c179b
· blocks 1
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#7
forward
#9
setData
#10
0x59558d29
#4
batchUpdate
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8708247…6a0a
0x34b655…2a6f
4 touches
1 conflict
0xcd0e796c…8200
0x34b655…2a6f
4 touches
1 conflict
0x178fe051…465a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3732c6c9…ded6
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
2 touches
0 conflicts
0x1b60b708…5b4b
0x2b46c0…1669
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
0xc8708247ab…8d6a0a
Audit this contract →
← previous block
·
next block →
recent activity