pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,732,983
← previous block
next block →
recent activity
Analyzing
Block #97,732,983
10 transactions · 8 stateful · 2026-08-20 21:40:07 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,732,983
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0x32d01e04
· blocks 1
#3
execOrder
#4
execFwdPositionOpsV2
#6
forward
#7
setData
#8
execOrders
#5
0x3f5c179b
#9
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x018ac2a6…71fb
0x34b655…2a6f
2 touches
0 conflicts
0x0494220d…abf6
0x34b655…2a6f
2 touches
0 conflicts
0x0494220d…abf7
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:
0xc1570aa1…7ac91b
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity