pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,131,617
← previous block
next block →
recent activity
Analyzing
Block #91,131,617
9 transactions · 9 stateful · 2026-07-28 18:40:05 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,131,617
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
0x3f5c179b
#4
executeBatch
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
setData
#8
execOrders
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0x0dd86a57…27bd
0x34b655…2a6f
2 touches
0 conflicts
0x3697da4a…4eb7
0x34b655…2a6f
2 touches
0 conflicts
0x49fc2bf5…7d91
0x34b655…2a6f
2 touches
0 conflicts
0x4f958f05…6b0f
0x34b655…2a6f
2 touches
0 conflicts
0x57330c5d…9973
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
0x7aad02c682…feb979
Audit this contract →
← previous block
·
next block →
recent activity