pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,773,764
← previous block
next block →
recent activity
Analyzing
Block #92,773,764
13 transactions · 13 stateful · 2026-08-03 12:23:40 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,773,764
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6a7088c4
#3
matchOrders
· blocks 1
#5
execOrders
· blocks 1
#6
updatePrices
#7
execFwdPositionOps
#8
executeBatch
#9
setData
#11
0x59558d29
#12
0xc7e3ec2c
#4
matchOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80da9050…c5a8
0x34b655…2a6f
4 touches
1 conflict
0xaab01f1e…e832
0x34b655…2a6f
4 touches
1 conflict
0x1af53e83…c72e
0x754704…b603
4 touches
1 conflict
0x7e8cd4a2…8fc0
0x754704…b603
4 touches
1 conflict
0xee8f5c15…6148
0x754704…b603
4 touches
1 conflict
0x4f197b72…35ab
0x99c7a7…8bf0
4 touches
1 conflict
0x7effde98…3ca2
0x99c7a7…8bf0
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
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
0x80da9050a4…b9c5a8
Audit this contract →
← previous block
·
next block →
recent activity