pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,592,810
← previous block
next block →
recent activity
Analyzing
Block #93,592,810
9 transactions · 8 stateful · 2026-08-06 09:04:08 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,592,810
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0xb2d4797b
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#7
setData
#8
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c702894…9f4c
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x64ac7e40…5d7d
0x34b655…2a6f
2 touches
0 conflicts
0x6be37e18…14e1
0x34b655…2a6f
2 touches
0 conflicts
0x78b52df8…344b
0x34b655…2a6f
2 touches
0 conflicts
0x806a06fb…4ce1
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
0x4c70289445…3e9f4c
Audit this contract →
← previous block
·
next block →
recent activity