pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,561,756
← previous block
next block →
recent activity
Analyzing
Block #97,561,756
11 transactions · 11 stateful · 2026-08-20 07:06:59 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,561,756
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
setData
#3
execOrders
· blocks 2
#4
updatePrices
#7
forward
#8
0xed82b078
#9
0x59558d29
#5
execFwdPositionOpsV2
· blocks 1
#10
0x7b84f330
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
5
w1
6
w2
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x82eb45d1…8f6a
0x34b655…2a6f
4 touches
1 conflict
0x8a06d70a…8ba3
0x34b655…2a6f
4 touches
1 conflict
0x9a46867d…30c0
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
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