pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,958,622
← previous block
next block →
recent activity
Analyzing
Block #94,958,622
10 transactions · 10 stateful · 2026-08-11 03:50:52 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,958,622
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
#3
0x222d4ad6
#4
placeAndExecuteMarketBuy
· blocks 1
#6
execOrders
#7
0x6a7a9c93
#8
transfer
#9
setData
#5
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xedbe4a92…8c3e
0x851145…3f07
4 touches
1 conflict
0x01dada3b…0aa8
0x34b655…2a6f
2 touches
0 conflicts
0x06a0c880…707b
0x34b655…2a6f
2 touches
0 conflicts
0x0db11951…d3e6
0x34b655…2a6f
2 touches
0 conflicts
0x19439a65…eb51
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity