pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,201,878
← previous block
next block →
recent activity
Analyzing
Block #95,201,878
8 transactions · 6 stateful · 2026-08-12 00:15:15 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,201,878
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
placeAndExecuteMarketSell
#3
placeAndExecuteMarketSell
#4
execFwdPositionOps
#6
setData
#7
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe34553e…8485
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x24b08f9c…e594
0x34b655…2a6f
2 touches
0 conflicts
0x53aa0415…4455
0x34b655…2a6f
2 touches
0 conflicts
0x550e12cc…8985
0x34b655…2a6f
2 touches
0 conflicts
0x87328177…9bfd
0x34b655…2a6f
2 touches
0 conflicts
0x898d9b8a…d1ef
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
0xbe34553ee6…f08485
Audit this contract →
← previous block
·
next block →
recent activity