pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,246,960
← previous block
next block →
recent activity
Analyzing
Block #99,246,960
8 transactions · 8 stateful · 2026-08-26 05:35:51 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,246,960
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8263f5d9
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
#4
claim
· blocks 1
#6
setData
#7
execOrders
#5
0xc925b3a5
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
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x990b3d60…7fe9
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x990b3d60…7fea
0x8964d7…10f8
3 touches
1 conflict
0x62811193…1868
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186e
0x2b46c0…1669
2 touches
0 conflicts
0x6cd67eff…f738
0x2b46c0…1669
2 touches
0 conflicts
0x915c095e…c1e5
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:
0x8964d7c9…5b10f8
1 conflict on slot
0x0000000000…000008
Audit this contract →
← previous block
·
next block →
recent activity