pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,364,982
← previous block
next block →
recent activity
Analyzing
Block #93,364,982
13 transactions · 13 stateful · 2026-08-05 13:58:47 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,364,982
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrder
· blocks 1
#3
0x5acec890
#5
execFwdPositionOps
#6
updatePriceFeedsIfNecessary
#7
forward
#8
0xed82b078
#9
updateDataFeedsValuesPartial
#10
0x6a73420f
#11
setData
#12
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a7
0x34b655…2a6f
4 touches
1 conflict
0xa8cd789b…bdfd
0x34b655…2a6f
4 touches
1 conflict
0x46ee3c65…4ab8
0x34b655…2a6f
3 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
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
0x898d9b8ab1…f9d1ef
Audit this contract →
← previous block
·
next block →
recent activity