pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,953,064
← previous block
next block →
recent activity
Analyzing
Block #99,953,064
12 transactions · 11 stateful · 2026-08-28 17:03:58 UTC
Parallelism
83
/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,953,064
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x59558d29
#4
execPerpOps
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
claim
· blocks 1
#9
0x6a91bff5
#10
setData
#11
0xef5bcd…76c5
#8
0xc925b3a5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e37cee0…14de
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x5e37cee0…14df
0x8964d7…10f8
3 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
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:
0x8964d7c9…5b10f8
1 conflict on slot
0x5e37cee06c…2f14de
Audit this contract →
← previous block
·
next block →
recent activity