pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,229,064
← previous block
next block →
recent activity
Analyzing
Block #93,229,064
9 transactions · 7 stateful · 2026-08-05 02:35:24 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,229,064
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#7
setData
#8
execOrders
#5
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa9c420e…8b45
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x334aa47d…cac0
0x34b655…2a6f
2 touches
0 conflicts
0x342fc7e5…c7c7
0x34b655…2a6f
2 touches
0 conflicts
0x53826bef…9b28
0x34b655…2a6f
2 touches
0 conflicts
0x565326bb…ae7e
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
0xaa9c420e05…248b45
Audit this contract →
← previous block
·
next block →
recent activity