pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,420,819
← previous block
next block →
recent activity
Analyzing
Block #93,420,819
9 transactions · 6 stateful · 2026-08-05 18:39:31 UTC
Parallelism
67
/100
Blocked
50
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,420,819
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
· blocks 1
#3
execOrder
· blocks 2
#5
updateDataFeedsValuesPartial
#6
batchCancelOrders
#8
setData
#2
matchOrders
#4
execOrders
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xecf72a3c…67a3
0x34b655…2a6f
4 touches
1 conflict
0x1c795b3a…8e8a
0x754704…b603
4 touches
1 conflict
0x3a473699…6159
0x754704…b603
4 touches
1 conflict
0x8434d4d0…d5d8
0x754704…b603
4 touches
1 conflict
0x8743e1ba…8331
0x34b655…2a6f
4 touches
1 conflict
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity