pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,007,628
← previous block
next block →
recent activity
Analyzing
Block #95,007,628
12 transactions · 12 stateful · 2026-08-11 07:57:21 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,007,628
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
execOrders
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#5
placeAndExecuteMarketSell
· blocks 1
#8
batchUpdate
#9
setData
#10
0x59558d29
· blocks 1
#6
placeAndExecuteMarketSell
#7
execFwdPositionOps
#11
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf633609…c3e5
0x851145…3f07
4 touches
1 conflict
0xacea03ce…0f23
0x34b655…2a6f
4 touches
1 conflict
0xe58009e8…fe3f
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
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:
0x851145ea…9f3f07
1 conflict on slot
0xaf633609ea…45c3e5
Audit this contract →
← previous block
·
next block →
recent activity