pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,450,599
← previous block
next block →
recent activity
Analyzing
Block #93,450,599
10 transactions · 10 stateful · 2026-08-05 21:09:14 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,450,599
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0x5acec890
· blocks 2
#4
execFwdPositionOps
· blocks 1
#6
placeAndExecuteMarketSell
#7
setData
#9
0x59558d29
#2
matchOrders
#5
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7effde98…3ca2
0x99c7a7…8bf0
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd7f2bb8f…b7d5
0x34b655…2a6f
4 touches
1 conflict
0xdfc21d7c…e062
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
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:
0x99c7a72e…c78bf0
1 conflict on slot
0x7effde98ef…713ca2
Audit this contract →
← previous block
·
next block →
recent activity