pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,232,725
← previous block
next block →
recent activity
Analyzing
Block #93,232,725
9 transactions · 9 stateful · 2026-08-05 02:53:49 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
#93,232,725
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
0x3f5c179b
#6
execFwdPositionOps
#7
0x6a72a634
#8
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x95649081…c6a9
0x34b655…2a6f
3 touches
1 conflict
0x006bb03b…ee43
0x34b655…2a6f
3 touches
1 conflict
0x0617b188…8052
0x34b655…2a6f
2 touches
0 conflicts
0x0e4000ee…afb9
0x34b655…2a6f
2 touches
0 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
2 touches
0 conflicts
0x27099c8c…d9d5
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
0x4e8c4408ae…50d37a
Audit this contract →
← previous block
·
next block →
recent activity