pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,026,134
← previous block
next block →
recent activity
Analyzing
Block #96,026,134
10 transactions · 8 stateful · 2026-08-14 21:36:11 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,026,134
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
aggregate3Value
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5acec890
· blocks 1
#5
aggregate3
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3ff1e5e…fd27
0x34b655…2a6f
4 touches
1 conflict
0x5fab7fbe…1ce5
0x34b655…2a6f
4 touches
1 conflict
0xc751242c…efac
0x34b655…2a6f
4 touches
1 conflict
0xb1a0dd74…f087
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0x6270a640…122e
0x1c8a33…d316
2 touches
0 conflicts
0x10b8d161…8791
0x754704…b603
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
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
0xd3ff1e5e32…68fd27
Audit this contract →
← previous block
·
next block →
recent activity