pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,903,136
← previous block
next block →
recent activity
Analyzing
Block #94,903,136
12 transactions · 10 stateful · 2026-08-10 23:11:47 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,903,136
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
execFwdPositionOps
· blocks 1
#5
repayWithCollateral
#6
placeAndExecuteMarketBuy
#7
0x3f5c179b
#8
0x3f5c179b
#9
execOrders
#10
setData
#11
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f8644f7…10fa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x6507044e…bcd6
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
2 touches
0 conflicts
0x19795ad6…4a16
0x34b655…2a6f
2 touches
0 conflicts
0x1c7f2eca…cf5e
0x34b655…2a6f
2 touches
0 conflicts
0x23b06bf5…1693
0x34b655…2a6f
2 touches
0 conflicts
0x23b06bf5…1694
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
0x6f8644f7cb…ae10fa
Audit this contract →
← previous block
·
next block →
recent activity