pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,202,294
← previous block
next block →
recent activity
Analyzing
Block #99,202,294
13 transactions · 11 stateful · 2026-08-26 01:51:07 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,202,294
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
execOrders
#4
0x59558d29
#5
execPerpOps
· blocks 1
#7
execFwdPositionOpsV2
#8
0x3f5c179b
#9
setData
#10
0x36326531
#11
execOrders
#12
execOrders
#6
execPerpOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x26d8622c…e8af
0x34b655…2a6f
2 touches
0 conflicts
0x41c56387…a8f6
0x34b655…2a6f
2 touches
0 conflicts
0x4ed096a7…1c6c
0x34b655…2a6f
2 touches
0 conflicts
0x631b4113…baa9
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
0x6ca15e14f4…917be8
Audit this contract →
← previous block
·
next block →
recent activity