pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,592,400
← previous block
next block →
recent activity
Analyzing
Block #93,592,400
12 transactions · 12 stateful · 2026-08-06 09:02:04 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,592,400
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 2
#3
0x5acec890
#4
0x3f5c179b
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0xe9316489
#10
setData
#5
execFwdPositionOps
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8218911e…3bed
0x34b655…2a6f
6 touches
3 conflicts
0xc9eaa844…2344
0x34b655…2a6f
4 touches
1 conflict
0x000bde1a…e123
0x34b655…2a6f
4 touches
1 conflict
0x1e56f6b6…5940
0x34b655…2a6f
4 touches
1 conflict
0x22755bc3…3056
0x34b655…2a6f
4 touches
1 conflict
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0x80656e3b…9240
0x34b655…2a6f
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
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
3 conflicts on slot
0x8218911eb6…d93bed
Audit this contract →
← previous block
·
next block →
recent activity