pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,037,853
← previous block
next block →
recent activity
Analyzing
Block #99,037,853
8 transactions · 8 stateful · 2026-08-25 12:00:07 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,037,853
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
updatePriceFeedsIfNecessary
#4
execFwdPositionOpsV2
· blocks 1
#6
0x57368ddf
#7
execOrders
#5
execFwdPositionOpsV2
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
0xbad4e90b…33a5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x295780b7…d2d1
0x34b655…2a6f
4 touches
1 conflict
0x46e2bb67…d8b3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2f4b2cf9…4e1e
0x2b46c0…1669
2 touches
0 conflicts
0x7aa91b8f…d070
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6a9e
0x2b46c0…1669
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
0xbad4e90ba6…2233a5
Audit this contract →
← previous block
·
next block →
recent activity