pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,456,684
← previous block
next block →
recent activity
Analyzing
Block #93,456,684
15 transactions · 13 stateful · 2026-08-05 21:39:49 UTC
Parallelism
87
/100
Blocked
31
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,456,684
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
withdraw
· blocks 1
#7
execFwdPositionOps
· blocks 2
#9
0x3f5c179b
#10
execOrders
#11
setData
#13
0x59558d29
· blocks 1
#6
withdraw
#8
execFwdPositionOps
#12
execOrders
#14
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w0
8
w1
12
w1
13
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x0a000000…0001
0x000000…1000
3 touches
1 conflict
0x1b49f420…7fe1
0x34b655…2a6f
2 touches
0 conflicts
0x1cdfe548…d3aa
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
0xb4e0a934b9…435fc7
Audit this contract →
← previous block
·
next block →
recent activity