pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,467,537
← previous block
next block →
recent activity
Analyzing
Block #93,467,537
11 transactions · 8 stateful · 2026-08-05 22:34:23 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,467,537
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
execOrders
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#7
placeAndExecuteMarketSell
#9
0x6a73bae7
#10
setData
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8743e1ba…8331
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x4102cb2a…3b17
0x34b655…2a6f
2 touches
0 conflicts
0x4c3f517f…1230
0x34b655…2a6f
2 touches
0 conflicts
0x7ac265cd…0253
0x34b655…2a6f
2 touches
0 conflicts
0x80398c66…f3cc
0x34b655…2a6f
2 touches
0 conflicts
0x91b0f8ed…6bd6
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
0x8743e1bab8…0a8331
Audit this contract →
← previous block
·
next block →
recent activity