pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,475,690
← previous block
next block →
recent activity
Analyzing
Block #93,475,690
9 transactions · 7 stateful · 2026-08-05 23:15:22 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,475,690
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrder
· blocks 1
#3
execOrders
· blocks 1
#4
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#8
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b9bb4b…145a
0x34b655…2a6f
4 touches
1 conflict
0x875bed31…14d9
0x34b655…2a6f
4 touches
1 conflict
0x2f358e74…1022
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x921b58ec…779c
0x34b655…2a6f
2 touches
0 conflicts
0x961096d6…2a46
0x34b655…2a6f
2 touches
0 conflicts
0x971e828f…7a69
0x34b655…2a6f
2 touches
0 conflicts
0xbcbf5d09…8bac
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
0xc6b9bb4b8d…cc145a
Audit this contract →
← previous block
·
next block →
recent activity