pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,708,040
← previous block
next block →
recent activity
Analyzing
Block #96,708,040
5 transactions · 5 stateful · 2026-08-17 06:46:15 UTC
Parallelism
60
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,708,040
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeb282f7f
#2
execFwdPositionOpsV2
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execOrders
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
0x2b8d9898…d525
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0xa44872f6…db0a
0x1efe02…37d6
2 touches
0 conflicts
0xe7d5a741…cddb
0x1efe02…37d6
2 touches
0 conflicts
0x0313aedc…bfaf
0x34b655…2a6f
2 touches
0 conflicts
0x0313aedc…bfb0
0x34b655…2a6f
2 touches
0 conflicts
0x0784e00e…e193
0x34b655…2a6f
2 touches
0 conflicts
0x0939bc15…c5e8
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
1 conflict on slot
0x2b8d9898a3…ecd525
Audit this contract →
← previous block
·
next block →
recent activity